Data center relocation methods and apparatus

ABSTRACT

Methods and apparatus for supporting a data center relocation with regard to an access point are described. A primary gateway connection is established between the access point and a primary gateway in a first data center, and a secondary gateway connection is established between the access point and a secondary gateway in a second data center. A path switch request is sent via the secondary gateway connection. A DNS server sends an IP address corresponding to the second data center. The data center for the access point is switched from the first data center to the second data center. In some embodiments, the transition from the first data center to the second data center is in response to a detected communications failure. In other embodiments, the transition from the first data center to the second data center is due to scheduled maintenance.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 14/469,562, filed Aug. 26, 2014 which is hereby expresslyincorporated by reference in its entirety.

FIELD

Various embodiments relate to communication methods and apparatus and,more particularly, to methods and apparatus facilitating data centerrelocation for an access point.

BACKGROUND

Users with mobile devices are demanding ever increasing amounts of datafrom the wireless cellular systems to which they connect. This explosivegrowth has fueled the need for increasing amounts of cellularinfrastructure, in particular a dramatically increased density ofwireless access points (APs). To attempt to meet these increasingdemands, there is a trend to substantially increase the number ofavailable low power small cell APs, e.g., small cell Home eNodeBs(HeNBs). The small cells may be, and in some embodiments are,implemented as femto cells which share frequency spectrum with macrocells where an individual macrobase station normally corresponds to amacro cell.

In the macro network a fair amount of redundancy exists allowing forcontrol and/or other entities to take over and replace a failed node. Incurrent small cell deployments there tends to be little or noredundancy.

If small cells are to be viewed as a viable alternative to large cells,it should be appreciated that there is a need for methods and apparatuswhich would support redundancy and/or maintenance of small cell systemswithout placing significant burdens on macro network infrastructureelements that may already exist.

Thus, as small cells are deployed in larger numbers there is a need forredundancy and/or the ability to transition a UE (User Equipment device)or other device from one data center to another even though it maycontinue to receive services though a particular HeNB. It would bedesirable if such transitions of UEs could be implemented withrelatively little signaling or communication with elements of the macronetwork when the transition is between one data center serving HeNBs toanother data center serving HeNBs and an HeNB serving a UE remainsunchanged.

Accordingly, given that an active data center may fail and/or need to beremoved from active status to support maintenance, there is a need formethods and apparatus that facilitate moving of UEs being serviced byHeNBs with communications links to one data center to another datacenter.

SUMMARY

Various embodiments are directed to methods and apparatus for supportingefficient transitions between datacenters, e.g., changing of datacenters responsible for servicing one or more small cells and UEsattached thereto. The small cells may, and in some embodiments are,femto cells.

In various embodiments, a plurality of data centers in a communicationsnetwork are deployed to support a large number of HeNBs. The datacenters may be implemented and managed separately from those of a macronetwork with which the femto cells, e.g., HeNBs, share frequencyspectrum. In this way, the data centers can service the HeNBs whilereducing or minimizing the amount of signaling to macro network elementsas part of supporting multiple HeNBs and the UEs connected thereto. Thedata centers may help limit or reduce the amount of signaling to macronetwork entities even when large numbers of small cells, e.g., HeNBs,are deployed. The data centers can be, and in various embodiments are,used to provide communications service to UEs, including possiblelocation tracking and other communications functions. While the UE's mayalso interact with macro base stations which generally service a largerservice area than HeNBs and/or communicate via an HeNB with a UE (userequipment) device the use of femto base stations and data centers canreduce the load on the macro network infrastructure but still providegenerally reliable communications services particularly when data centerredundancy is provided in accordance with various features andembodiments.

At least some of the methods and apparatus are well suited for smallcell deployments where one or more HeNBs rely on a data center toprovide signaling and/or communications related services and where itmay be desirable for redundancy and/or maintenance reasons to be able totransition UEs and small cells from one data center to another datacenter.

In various embodiments, an access point, e.g., an HeNB, establishes aprimary connection, e.g., a primary transport connection, with a firstHGW in a first datacenter, and establishes a secondary connection, e.g.,a secondary transport connection, with a second HGW, in a seconddatacenter.

In some embodiments, in response to detection of a primary gatewaycommunications failure, a path switch request via the secondaryconnection is used to transition from the first datacenter to the seconddatacenter.

In one exemplary embodiment, different DNSs (Domain Name System servers)in different datacenters map a tracking area in which an access pointmay be located to different IP addresses corresponding to differentdatacenters. In some such embodiments priority indicators are used inaddition to the IP address.

In another exemplary embodiment, a management device generates andtransmits dynamic DNS update messages, which are sent to DNS servers tochange mapping information and redirect between data centers, e.g., inresponse to a detected fault condition at a datacenter or in accordancewith scheduled maintenance.

An exemplary communications method, in accordance with some embodiments,includes: establishing a primary gateway connection between an accesspoint and a primary gateway; establishing a connection for a userequipment (UE) device to said access point, said established connectionbeing between said UE device and said access point; and transmitting apath switch request via a secondary gateway connection between saidaccess point and a secondary gateway, to a network entity, for said UEdevice connected to said access point while said UE device remainsconnected to said access point.

An exemplary communications system, in accordance with some embodiments,includes an access point comprising: a module configured to establish aprimary gateway connection between the access point and a primarygateway; a module configured to establish a connection for a userequipment (UE) device to said access point, said established connectionbeing between said UE device and said access point; a transmitter; and amodule configured to control the transmitter to transmit a path switchrequest via a secondary gateway connection between said access point anda secondary gateway, to a network entity, for said UE device connectedto said access point while said UE device remains connected to saidaccess point.

While various embodiments have been discussed in the summary above, itshould be appreciated that not necessarily all embodiments include thesame features and some of the features described above are not necessarybut can be desirable in some embodiments. Numerous additional features,embodiments, and benefits of various embodiments are discussed in thedetailed description which follows.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 is a drawing of an exemplary communications system in accordancewith an exemplary embodiment.

FIG. 2 includes a drawing which illustrates exemplary signaling andexemplary steps in accordance with an exemplary embodiment in which anaccess point detects a primary gateway communications failure.

FIG. 3 includes a drawing which illustrates exemplary signaling andexemplary steps in accordance with an exemplary embodiment in which amanagement device detects a primary gateway communications failure.

FIG. 4 includes a drawing which illustrates exemplary signaling andexemplary steps in accordance with an exemplary embodiment in which amanagement device generates and transmits a dynamic Domain Name Server(DNS) update message in response to a detected primary gatewaycommunication failure.

FIG. 5 includes a drawing which illustrates exemplary signaling andexemplary steps in accordance with an exemplary embodiment in which amanagement device generates and transmits a dynamic DNS update messagein response to scheduled maintenance.

FIG. 6 is a flowchart of an exemplary communications method inaccordance with an exemplary embodiment in which an access point detectsa primary gateway communications failure.

FIG. 7 is a flowchart of an exemplary communications method inaccordance with an exemplary embodiment in which a management devicedetects a primary gateway communications failure.

FIG. 8 is a flowchart of an exemplary communications method inaccordance with an exemplary embodiment in which a management devicegenerates and transmits a dynamic DNS update message in response to adetected primary gateway communication failure.

FIG. 9 is a flowchart of an exemplary communications method inaccordance with an exemplary embodiment in which a management devicegenerates and transmits a dynamic DNS update message in response toscheduled maintenance.

FIG. 10 is a flowchart of an exemplary communications method inaccordance with an exemplary embodiment in which a management devicegenerates and transmits a dynamic DNS update message in response toscheduled maintenance.

FIG. 11 is a drawing illustrating exemplary mapping tables which may beincluded in exemplary DNSs in accordance with an exemplary embodiment.

FIG. 12 is a drawing illustrating exemplary original and updated mappingtables which may be included in exemplary DNSs in accordance withanother exemplary embodiment.

FIG. 12A is a drawing illustrating exemplary original and updatedmapping tables which may be included in exemplary DNSs in accordancewith yet another exemplary embodiment.

FIG. 13 is a drawing illustrating exemplary original mapping tableswhich may be included in exemplary DNSs in accordance with anotherexemplary embodiment.

FIG. 13A is a drawing illustrating exemplary updated mapping tableswhich may be included in exemplary DNSs in accordance with the anotherexemplary embodiment.

FIG. 14 is a drawing of an exemplary access point, e.g., a HeNB, inaccordance with an exemplary embodiment.

FIG. 15 is a drawing of an assembly of modules which may be included inan exemplary access point, e.g., a HeNB, in accordance with an exemplaryembodiment.

FIG. 16 is a drawing of an exemplary DNS, e.g, a secondary DNS server,in accordance with an exemplary embodiment.

FIG. 17 is a drawing of an assembly of modules which may be included inan exemplary DNS server of FIG. 16 in accordance with an exemplaryembodiment.

FIG. 18 is a drawing of an exemplary management device in accordancewith an exemplary embodiment.

FIG. 19 is a drawing of an assembly of modules which may be included inan exemplary management device in accordance with an exemplaryembodiment.

FIG. 20 is a drawing of an exemplary DNS server, e.g., a primary DNSserver, in accordance with an exemplary embodiment.

FIG. 21 is a drawing of an assembly of modules which may be included inan exemplary DNS server of FIG. 20 in accordance with an exemplaryembodiment.

FIG. 22 is a drawing of an exemplary DNS server, e.g., a DNS server in aservice provider datacenter, in accordance with an exemplary embodiment.

FIG. 23 is a drawing of an assembly of modules which may be included inan exemplary DNS server of FIG. 22 in accordance with an exemplaryembodiment.

FIG. 24 is a drawing of an exemplary Home Gateway (HGW), in accordancewith an exemplary embodiment.

FIG. 25 is a drawing of an assembly of modules which may be included inthe HGW of FIG. 24 in accordance with an exemplary embodiment.

FIG. 26 is a drawing of an exemplary mobile node, e.g., a user equipment(UE) device, in accordance with an exemplary embodiment.

FIG. 27 is a drawing of an assembly of modules which may be included inthe mobile node of FIG. 26 in accordance with an exemplary embodiment.

DETAILED DESCRIPTION

FIG. 1 is a drawing of an exemplary communications system 100 inaccordance with an exemplary embodiment. Exemplary communications system100 includes a service provider datacenter 102, a plurality ofdatacenters (datacenter 1, . . . , datacenter M 106, a plurality ofaccess points which are Home eNodeBs (HeNB 1, . . . , HeNB N 110), and aplurality of user equipment devices (UE 1 134, . . . , UE 4 136, UE 5140, . . . , UE n 144). In some embodiments, communications system 100further includes a management device 125.

Service provider datacenter 102, e.g., an EPC datacenter, include apacket data network gateway (PGW) 112, a serving gateway (SGW) 114, amobility management entity (MME) 116, and domain name server (DNS) 115.Datacenter 1 104 includes DNS 1 118, SGW 1 122, and HGW 1 124.Datacenter M 106 includes DNS M 128, SGW M 130, and HGW M 132. Serviceprovider datacenter 102 is coupled to datacenter 1 104, as indicated bybi-directional arrow 166. Service provider datacenter 102 is coupled todatacenter M 106, as indicated by bi-directional arrow 168. In oneexample M=2.

A plurality of UE devices (UE 1 134, . . . , UE 4 136) are coupled toHeNB 1 108, as indicated by bi-directional arrows (150, 152),respectively. A plurality of UE devices (UE 5 140, . . . , UE n 144) arecoupled to HeNB N 110, as indicated by bi-directional arrows (154, 156),respectively.

Each HeNB may, and sometimes does, establish connections with multipleHGWs corresponding to different datacenters. HeNB 1 108 is shown havingan established primary connection 158, e.g., a primary transportconnection, with HGW1 124, and HeNB 1 108 is shown having an establishedsecondary connection 160, e.g., a secondary transport connection, withHGW M 132. HeNB N 110 is shown having an established primary connection162, e.g., a primary transport connection, with HGW M 132, and HeNB N110 is shown having an established secondary connection 164, e.g., asecondary transport connection, with HGW 1 124.

In some embodiments, HeNB 1 108 is located in a first tracking area andHeNB N 110 is located in a second tracking area. In some suchembodiments, datacenter 1 104 serves as the primary datacenter for HeNB1 108; datacenter M 106 serves as the secondary or back-up datacenter ofHeNB 1 108; datacenter M 106 serves as the primary datacenter for HeNB N110; datacenter 1 104 serves as the secondary or back-up datacenter ofHeNB N 110. In various embodiments, switching between data centers isperformed in response to a detected failure or in response to scheduledmaintenance. The detected failure may be detected by an HeNB, e.g., HeNB1 108, or by the management device 125. In some embodiments, a userdevice, e.g., UE 1 134 in unaware that its HeNB, e.g., HeNB 1 108 hasswitched between datacenters.

Management device 125 monitors the datacenter operations for failures,monitors communications for failures, e.g., communications betweendatacenters and access points, for failures. In various embodiments,management device 125 generates and sends dynamic DNS update messages,e.g., to facilitate switching between datacenters.

FIG. 2 is a drawing illustrating an exemplary communications method inaccordance with an exemplary embodiment. Drawing 200 includes anexemplary user equipment (UE) device 134, an exemplary access point,HeNB 108, an exemplary first datacenter, datacenter 1 104, an exemplarysecond datacenter, datacenter 2 106, and exemplary service providerdatacenter 102, Datacenter 1 104 includes a home gateway, HGW 1 124, aserving gateway, SGW 1 122, and a domain name server, DNS 1 118.Datacenter 2 106 includes a home gateway, HGW 2 132, a serving gateway,SGW 2 130, and a domain name server, DNS 2 126. Service providerdatacenter 102 includes a mobility management entity (MME) 116. A packetdata network gateway (PGW) 112, and a domain name server, DNS 115.

In step 202 and step 204, HeNB 108 and HGW1 124, communicate signals toestablish a primary gateway connection for HeNB 108, which is primarytransport connection 203. In step 206 and step 208, HeNB 108 and HGW2132, communicate signals to establish a secondary gateway connection forHeNB 108, which is secondary transport connection 207. In step 210 andstep 212, UE 134 and HeNB 108 communicate signals to establish UEconnection 211.

In step 213 HeNB 108 monitors communications, and in step 213 a HeNB 108detects a primary gateway communications failure.

In step 214, in response to the detected primary gateway communicationsfailure, HeNB 108 generates and transmits a path switch request 215which is received by HGW 2 132 in step 216. In step 218, HGW 2 132generates and transmits path switch request 219, which is a forwardedversion of path switch request 215. In step 220 MME 116 receives pathswitch request 219.

In step 222, MME 116 generates and transmits a DNS request to resolvethe SGW information of the Tracking Area Identifier [TAI?] 223 to DNS115, which is received in step 224 by DNS 115 of service providerdatacenter 102. In step 226, DNS 115 generates and transmits DNS requestto resolve the SGW information of the Tracking Area Identifier[SGW-TAI?] 227 to DNS 2 126, which is received in step 228 by DNS 2 126.In step 230, DNS 115 generates and transmits a DNS request to resolvethe SGW information of the Tracking Area Identifier [SGW-TAI?] 231 toDNS 1 118, which is received in step 232 by DNS 1 118. In someembodiments, DNS request 227 and DNS request 231 communicate the samemessage via a broadcast message intended for a plurality of DNS servers,which may be located a plurality of datacenters.

In this example, the IP address corresponding to an SGW in the firstdata center is IP1 and the IP address corresponding to an SGW in thesecond data center is IP2.

In step 234, DNS 2 126 generates and transmits a DNS response resolvingthe SGW information of the Tracking Area Identifier into an IP addressIP2 [SGW-TAI→IP2] 235 to DNS 115, which is received in step 236. In thisexample, DNS 1 118, will not respond in the event of a primary datacenter failure, which is the situation. However, if there was no primarydata center failure then DNS 1 118 would have generated and transmitteda DNS response resolving the SGW information of the Tracking AreaIdentifier into an IP address IP1 [SGW-TAI→IP1]. DNS response 235includes a priority indicator indicating that the response has a lowerpriority than a response which may be provided by the primary DNSserver.

In this example, the secondary DNS, DNS 2 126, is responding but thesecondary DNS, DNS 2 126, has lower priority than the primary DNS, DNS 1118. However, the primary data center has failed so the secondary DNSwill be the only responder and will prevail.

In step 242, DNS 115 generates and transmits DNS response 243 to MME116, communicating IP2 which is received in step 244. In step 246, MME116 generates and transmits create session request 247 to SGW 2 130,which is received in step 248. In step 250 SGW 130 generates andtransmits modify session request 251 to PGW 112, which is received instep 252. In step 254, PGW 112 generates and transmits modify sessionresponse 255 to SGW 2 130, which is received in step 256. In step 258SGW 2 130 generates and transmits create session response 259 to MME116, which is received in step 260. In step 262, MME 116 generates andtransmits path switch request acknowledgments 263 to HGW 2 132, which isreceived in step 264. In step 266, HGW 2 132 generates and transmitspath switch request acknowledgment 267 to HeNB 108, which is received instep 268. In step 274, HeNB 108 generates and transmits UE contextrelease request 275 to HGW 1 124, which may be, and sometimes is,received in step 276. In some embodiments, UE context release request275 is sent in response to receiving path switch request acknowledgment.In some other embodiments, UE context release request 275 is sent inresponse to detection of primary gateway communications failure, e.g.,at a time subsequent to the detected failure. In some embodiments, UEcontext release request 275 is sent following transmission of the pathswitch request 216.

In step 270 MME 116 generates and transmits delete session request 271,which may be, and sometimes is, received by SGW 1 112 in step 272.

Assuming SGW 1 112 receives message 271, in step 278, SGW 1 122generates and transmits delete session response 279 to MME 116 which isreceived in step 280, by MME 116.

FIG. 3 is a drawing illustrating an exemplary communications method inaccordance with an exemplary embodiment. Drawing 300 includes anexemplary user equipment (UE) device 134′, an exemplary access point,HeNB 108′, an exemplary first datacenter, datacenter 1 104′, anexemplary second datacenter, datacenter 2 106′, and exemplary serviceprovider datacenter 102′, and an exemplary management device 125′.Datacenter 1 104′ includes a home gateway, HGW 1 124′, a servinggateway, SGW 1 122′, and a domain name server, DNS 1 118′. Datacenter 2106′ includes a home gateway, HGW 2 132′, a serving gateway, SGW 2 130′,and a domain name server, DNS 2 126′. Service provider datacenter 102′includes a mobility management entity (MME) 116′. A packet data networkgateway (PGW) 112′, and a domain name server, DNS 115′. The variouselements (134′, 108′, 104′ 106′ 102′, 124′, 122′, 118′, 132′, 130′,126′, 112′, 116′, 115′, 125′) shown in FIG. 3 may be the same or similarto elements (134, 108, 104, 106, 102, 124, 122, 118, 132, 130, 126, 112,116, 115, 125), respectively, shown in system 100 of FIG. 1.

In step 302 and step 304, HeNB 108′ and HGW1 124′, communicate signalsto establish a primary gateway connection for HeNB 108′, which isprimary transport connection 303. In step 306 and step 308, HeNB 108′and HGW2 132′, communicate signals to establish a secondary gatewayconnection for HeNB 108′, which is secondary transport connection 307.In step 310 and step 312, UE 134′ and HeNB 108′ communicate signals toestablish UE connection 311.

In step 313 management device 125′ monitors communications, and in step313 a management device 125′ detects a primary gateway communicationsfailure.

In step 313 b, management device 125′ generates and sends failurenotification message 313 c to HeNB 108′, which notifies the HeNB 108′ ofthe detected primary gateway communications failure. In step 313 d, HeNB108′ receives failure notification message 313 c.

In step 314, in response to the detected primary gateway communicationsfailure, HeNB 108′ generates and transmits a path switch request 315which is received by HGW 2 132′ in step 316. In step 318, HGW 2 132′generates and transmits path switch request 319, which is a forwardedversion of path switch request 315. In step 320 MME 116′ receives pathswitch request 319.

In step 322, MME 116′ generates and transmits a DNS request to resolvethe SGW information of the Tracking Area Identifier [TAI?] 323 to DNS115′, which is received in step 324 by DNS 115′ of service providerdatacenter 102′. In step 326, DNS 115′ generates and transmits a DNSrequest to resolve the SGW information of the Tracking Area Identifier[SGW-TAI?] 327 to DNS 2 126′, which is received in step 328 by DNS 2126′. In step 330, DNS 115′ generates and transmits a DNS request toresolve the SGW information of the Tracking Area Identifier [SGW-TAI?]331 to DNS 1 118′, which may be and sometimes is received in step 332 byDNS 1 118′. In some embodiments, DNS request 327 and DNS request 331communicate the same message via a broadcast message intended for aplurality of DNS servers, which may be located a plurality ofdatacenters.

In this example, the IP address corresponding to an SGW in the firstdata center is IP1 and the IP address corresponding to an SGW in thesecond data center is IP2.

In step 334, DNS 2 126′ generates and transmits a DNS response resolvingthe SGW information of the Tracking Area Identifier into an IP addressIP2 [SGW-TAI→IP2] 335 to DNS 115′, which is received in step 336. Inthis example, DNS 1 118′, will not respond in the event of a primarydata center failure, which is the situation. However, if there was noprimary data center failure then DNS 1 118′ would have generated andtransmitted a DNS response resolving the SGW information of the TrackingArea Identifier into an IP address IP1 [SGW-TAI→IP1]. DNS response 335includes a priority indicator indicating that the response has a lowerpriority than a response which may be provided by the primary DNSserver.

In this example, the secondary DNS, DNS 2 126′, is responding but thesecondary DNS, DNS 2 126′, has lower priority than the primary DNS, DNS1 118′. However, the primary data center has failed so the secondary DNSwill be the only responder and will prevail.

In step 342, DNS 115′ generates and transmits DNS response 343 to MME116′, communicating IP2 which is received in step 344. In step 346, MME116′ generates and transmits create session request 347 to SGW 2 130′,which is received in step 348. In step 350 SGW 130′ generates andtransmits modify session request 351 to PGW 112′, which is received instep 352. In step 354, PGW 112′ generates and transmits modify sessionresponse 355 to SGW 2 130′, which is received in step 356. In step 358SGW 2 130′ generates and transmits create session response 359 to MME116′, which is received in step 360. In step 362, MME 116′ generates andtransmits path switch request acknowledgments 363 to HGW 2 132′, whichis received in step 364. In step 366, HGW 2 132′ generates and transmitspath switch request acknowledgment 367 to HeNB 108′, which is receivedin step 368. In step 374, HeNB 108′ generates and transmits UE contextrelease request 375 to HGW 1 124′, which may be, and sometimes is,received in step 376. In some embodiments, UE context release request375 is sent in response to receiving path switch request acknowledgment.In some other embodiments, UE context release request 375 is sent inresponse to detection of primary gateway communications failure, e.g.,at a time subsequent to the detected failure. In some embodiments, UEcontext release request 375 is sent following transmission of the pathswitch request 316.

In step 370 MME 116′ generates and transmits delete session request 371,which may be, and sometimes is, received by SGW 1 112′ in step 372.

Assuming SGW 1 112′ receives message 371, in step 378, SGW 1 122′generates and transmits delete session response 379 to MME 116 which isreceived in step 380, by MME 116′.

FIG. 4 is a drawing illustrating an exemplary communications method inaccordance with an exemplary embodiment. Drawing 400 includes anexemplary user equipment (UE) device 134″, an exemplary access point,HeNB 108″, an exemplary first datacenter, datacenter 1 104″, anexemplary second datacenter, datacenter 2 106″, and exemplary serviceprovider datacenter 102″, and an exemplary management device 125″.Datacenter 1 104″ includes a home gateway, HGW 1 124″, a servinggateway, SGW 1 122″, and a domain name server, DNS 1 118″. Datacenter 2106′ includes a home gateway, HGW 2 132″, a serving gateway, SGW 2 130″,and a domain name server, DNS 2 126″. Service provider datacenter 102″includes a mobility management entity (MME) 116″. A packet data networkgateway (PGW) 112″, and a domain name server, DNS 115″. The variouselements (134″, 108″, 104″ 106″ 102″, 124″, 122″, 118″, 132″, 130″,126″, 112″, 116″, 115″, 125″) shown in FIG. 3 may be the same or similarto elements (134, 108, 104, 106, 102, 124, 122, 118, 132, 130, 126, 112,116, 115, 125), respectively, shown in system 100 of FIG. 1.

In step 402 and step 404, HeNB 108″ and HGW1 124″, communicate signalsto establish a primary gateway connection for HeNB 108′4, which isprimary transport connection 403. In step 406 and step 408, HeNB 108″and HGW2 132″, communicate signals to establish a secondary gatewayconnection for HeNB 108″, which is secondary transport connection 407.In step 410 and step 412, UE 134″ and HeNB 108″ communicate signals toestablish UE connection 411.

In step 413 management device 125″ monitors communications, and in step413 a management device 125″ detects a primary gateway communicationsfailure.

In step 413 b, management device 125″ generates and transmits dynamicDNS update message 413 c to DNS 115″, which is received in step 413 d byDNS 115″. In step 413 e, DNS 115″ updates stored information based onthe received information on message 413 c.

In step 413 f, management device 125″ generates and transmits dynamicDNS update message 413 g to DNS 1 118″, which is received in step 413 hby DNS 1 118″. In step 413 i, DNS 1 118″ updates stored informationbased on the received information on message 413 g.

In step 413 j, management device 125″ generates and transmits dynamicDNS update message 413 k to DNS 2 126″, which is received in step 413 lby DNS 2 126″. In step 413 m, DNS 2 126″ updates stored informationbased on the received information on message 413 k.

In some embodiments, not all three dynamic DNS updates may be requiredat the same time. The dynamic DNS updates are mostly complementary toeach other. In a first alternative, when the management device 125″ hasthe ability to send dynamic DNS updates directly to the DNS 115″ in theservice provider database 102″, a single dynamic DNS update 413 c isenough to update the serving GW (SGW) for the tracking area of the HeNB108″ to point to an SGW2 130″ in the second datacenter 106″, instead ofa SGW1 122″ in the first datacenter 104″. The pointing may be in theform of updating the name of the SGW responsible for the tracking area(from fully qualified name FQDN SGW1 to FQDN SGW2), while the resolutionof said FQDN into an IP address of the respective SGW can be carried onany authoritative server in the DNS infrastructure, including but notlimited to, in the service provider datacenter 102″, or in the primarydatacenter 104″ or secondary datacenter 106″.

In some embodiments, dynamic DNS update messages 413 c, 413 g and 413 kare the same message, e.g., communicated as a broadcast message to aplurality of DNS servers including DNS 115″, DNS 1 118″ and DNS 2 126″.

In various embodiments, the dynamic DNS update message communicates adynamic DNS update for the serving gateway (SGW) information of atracking area identifier corresponding to a location of access pointHeNB 108″, the dynamic DNS update including updating the serving gateway(SGW) information for said tracking area identifier to ultimatelyresolve into an IP address of a secondary SGW SGW2 130″ corresponding toa second data center, data center 2 106″, which is different from thefirst data center, data center 1 104″. For example, in one embodiment,the IP address corresponding to an SGW in the first data center is IP1and the IP address corresponding to an SGW in the second data center isIP2, and the dynamic DNS update message is used to move HeNB 108″ fromdata center 1 104″ to data center 2 106″ by changing the IP address forthe SGW in charge of the tracking area of HeNB 108″ from IP1 to IP2. Inanother exemplary embodiment, the domain name corresponding to an SGW inthe first data center is DomainName1 and the domain name correspondingto an SGW in the second data center is DomainName2, and the dynamic DNSupdate message is used to move HeNB 108″ from data center 1 104″ todatacenter 2 106″ by changing the domain name for the SGW in charge ofthe tracking area of HeNB 108″ from DomainName1 to DomainName2.

In some embodiments, the dynamic DNS update messages are used to changepriorities associated with the DNS servers. For example, dynamic DNSupdate message 413 g changes the priority associated with data center 1104″ from medium priority to low priority, and DNS update message 413 kchanges the priority associated with data center 2 106″ from lowpriority to high priority.

In some embodiments, the dynamic DNS update messages are used to changean IP address or domain name corresponding to a failed data center to anIP address or domain name corresponding to an operational data center.For example, dynamic DNS update message 413 g communicates an IP addressor domain name corresponding to datacenter 2 106″, which is to replacethe IP address or domain name corresponding to failed data center 1104″.

In some embodiments, dynamic DNS message 413 c is sent to DNS 115″, andDNS 115″ communicates information included message 413 c to one or moreof DNS 1 118″ and DNS 2 126″.

In step 413 n, management device 125″ generates and sends failurenotification message 413 o to HeNB 108″, which notifies the HeNB 108″ ofthe detected primary gateway communications failure. In step 413 p, HeNB108″ receives failure notification message 413 o.

In step 414, in response to the detected primary gateway communicationsfailure, HeNB 108″ generates and transmits a path switch request 415which is received by HGW 2 132″ in step 416. In step 418, HGW 2 132″generates and transmits path switch request 419, which is a forwardedversion of path switch request 415. In step 420 MME 116″ receives pathswitch request 419.

In step 422, MME 116″ generates and transmits a DNS request to resolvethe SGW information of the Tracking Area Identifier [TAI?] 423 to DNS115″, which is received in step 424 by DNS 115″ of service providerdatacenter 102″. In step 426, DNS 115″ generates and transmits a DNSrequest to resolve the SGW information of the Tracking Area Identifier[SGW-TAI?] 427 to DNS 2 126″, which is received in step 428 by DNS 2126″. In step 430, DNS 115″ generates and transmits a DNS request toresolve the SGW information of the Tracking Area Identifier [SGW-TAI?]431 to DNS 1 118″, which may be and sometimes is received in step 432 byDNS 1 118″. In some embodiments, DNS request 427 and DNS request 431communicate the same message via a broadcast message intended for aplurality of DNS servers, which may be located a plurality ofdatacenters.

In step 434, DNS 2 126″ generates and transmits a DNS response resolvingthe SGW information of the Tracking Area Identifier into an IP addressIP2 [SGW-TAI→IP2] 435 to DNS 115″, which is received in step 436. Inthis example, DNS 1 118″, will not respond in the event of a primarydata center failure, which is the situation. However, if there was noprimary data center failure then DNS 1 118″ would have generated andtransmitted a DNS response resolving the SGW information of the TrackingArea Identifier into an IP address IP1 [SGW-TAI→IP1]. DNS response 435includes a priority indicator indicating that the response has a lowerpriority than a response which may be provided by the primary DNSserver.

In this example, the secondary DNS, DNS 2 126″, is responding but thesecondary DNS, DNS 2 126″, has lower priority than the primary DNS, DNS1 118″. However, the primary data center has failed so the secondary DNSwill be the only responder and will prevail.

In step 442, DNS 115″ generates and transmits DNS response 443 to MME116″, communicating IP2 which is received in step 444. In step 446, MME116″ generates and transmits create session request 447 to SGW 2 130″,which is received in step 448. In step 450 SGW 130″ generates andtransmits modify session request 451 to PGW 112″, which is received instep 452. In step 454, PGW 112″ generates and transmits modify sessionresponse 455 to SGW 2 130″, which is received in step 456. In step 458SGW 2 130″ generates and transmits create session response 459 to MME116″, which is received in step 460. In step 462, MME 116″ generates andtransmits path switch request acknowledgments 463 to HGW 2 132″, whichis received in step 464. In step 466, HGW 2 132″ generates and transmitspath switch request acknowledgment 467 to HeNB 108″, which is receivedin step 468. In step 474, HeNB 108″ generates and transmits UE contextrelease request 475 to HGW 1 124″, which may be, and sometimes is,received in step 476. In some embodiments, UE context release request475 is sent in response to receiving path switch request acknowledgment.In some other embodiments, UE context release request 475 is sent inresponse to detection of primary gateway communications failure, e.g.,at a time subsequent to the detected failure. In some embodiments, UEcontext release request 475 is sent following transmission of the pathswitch request 416.

In step 470 MME 116″ generates and transmits delete session request 471,which may be, and sometimes is, received by SGW 1 112″ in step 472.

Assuming SGW 1 112″ receives message 471, in step 478, SGW 1 122″generates and transmits delete session response 479 to MME 116″ which isreceived in step 480, by MME 116″.

FIG. 5 is a drawing 500 illustrating an exemplary communications methodin accordance with an exemplary embodiment. Drawing 500 includes anexemplary user equipment (UE) device 134′″, an exemplary access point,HeNB 108′″, an exemplary first datacenter, datacenter 1 104′″, anexemplary second datacenter, datacenter 2 106′″, and exemplary serviceprovider datacenter 102′″, and an exemplary management device 125″Datacenter 1 104′″ includes a home gateway, HGW 1 124′″, a servinggateway, SGW 1 122′″, and a domain name server, DNS 1 118′″. Datacenter2 106′″ includes a home gateway, HGW 1 132′″, a serving gateway, SGW 2130′″, and a domain name server, DNS 2 126′″. Service providerdatacenter 102′″ includes a mobility management entity (MME) 116′″, apacket data network gateway (PGW) 112′″, and a domain name server, DNS115″. The various elements (134′″, 108′″, 104′″ 106′″ 102′″, 124′″,122′″, 118′″, 132′″, 130′″, 126′″, 112′″, 116′″, 115′″, 125′″) shown inFIG. 3 may be the same or similar to elements (134, 108, 104, 106, 102,124, 122, 118, 132, 130, 126, 112, 116, 115, 125), respectively, shownin system 100 of FIG. 1.

In step 502 and step 504, HeNB 108′″ and HGW1 124′″, communicate signalsto establish a primary gateway connection for HeNB 108′″, which isprimary transport connection 503. In step 506 and step 508, HeNB 108′″and HGW2 132′″, communicate signals to establish a secondary gatewayconnection for HeNB 108′″, which is secondary transport connection 507.In step 510 and step 512, UE 134′″ and HeNB 108′″ communicate signals toestablish UE connection 511.

In step 513 management device 125′″ determines it is time for ascheduled maintenance operation. For example, at this time it isdesirable that data center 1 104′″ be taken off line so that variousmaintenance operation can be performed.

In step 513 a, management device 125′″ generates and transmits dynamicDNS update message 513 b to DNS 115′″, which is received in step 513 cby DNS 115′″. In step 513 d, DNS 115′″ updates stored information basedon the received information on message 513 b.

In step 513 e, management device 125′″ generates and transmits dynamicDNS update message 513 f to DNS 1 118′″, which is received in step 513 gby DNS 1 118′″. In step 513 h, DNS 1 118″ updates stored informationbased on the received information on message 513 f.

In step 513 i, management device 125′″ generates and transmits dynamicDNS update message 513 j to DNS 2 126′″, which is received in step 513 kby DNS 2 126″. In step 513 l, DNS 2 126′″ updates stored informationbased on the received information on message 413 j.

In some embodiments, dynamic DNS update messages 513 b, 513 f and 513 jare the same message, e.g., communicated as a broadcast message to aplurality of DNS servers including DNS 115′″, DNS 1 118′″ and DNS 2126′″.

In various embodiments, the dynamic DNS update message communicates adynamic DNS update for the serving gateway (SGW) information of atracking area identifier corresponding to a location of access pointHeNB 108′″, the dynamic DNS update including updating the servinggateway (SGW) information for said tracking area identifier toultimately resolve into an IP address of a secondary SGW SGW2 130′″ anIP address corresponding to a second data center, data center 2 106′″,which is different from the first data center, data center 1 104′″. Forexample, in one embodiment, the IP address corresponding to an SGW inthe first data center is IP1 and the IP address corresponding to an SGWin the second data center is IP2, and the dynamic DNS update message isused to move HeNB 108′″ from data center 1 104′″ to data center 2 106′″by changing the IP address for the SGW in charge of the tracking area ofHeNB 108′″ from IP1 to IP2. In another exemplary embodiment, the domainname of corresponding to an SGW in the first data center is DomainName1and the domain name corresponding to an SGW in the second data center isDomainName2, and the dynamic DNS update message is used to move HeNB108′ from data center 1 104′ to datacenter 2 106′ by changing the domainname for the SGW in charge of the tracking area of HeNB 108″ fromDomainName1 to DomainName2.

In some embodiments, the dynamic DNS update messages are used to changepriorities associated with the DNS servers. For example, dynamic DNSupdate message 513 f changes the priority associated with data center 1104′″ from medium priority to low priority, and DNS update message 513 jchanges the priority associated with data center 2 106′″ from lowpriority to high priority.

In some embodiments, the dynamic DNS update messages are used to changean IP address or domain name corresponding to a data center beingintentionally taken off line, e.g., for maintenance to an IP address ordomain name corresponding to an operational data center. For example,dynamic DNS update message 513 f communicates and IP address or domainname corresponding to datacenter 2 106′″, which is to replace the IPaddress corresponding to data center 1 104′″, which is being taken offline for maintenance.

In some embodiments, dynamic DNS message 513 b is sent to DNS 115′″, andDNS 115′″ communicates information included message 513 b to one of moreof DNS 1 118′″ and DNS 2 126′″.

In step 513 m, management device 125′″ generates and sends notificationmessage 513 n to HeNB 108′″, which notifies the HeNB 108′″ that datacenter 1 104″ is going to be taken off line, e.g., for maintenance. Instep 513 o, HeNB 108′ receives notification message 513 n.

In step 514, e.g., in response to the notification message or inresponse to a detected off line condition of datacenter 1 104′″, HeNB108′ generates and transmits a path switch request 515 which is receivedby HGW 2 132′ in step 516. In step 518, HGW 2 132′ generates andtransmits path switch request 519, which is a forwarded version of pathswitch request 515. In step 520 MME 116′″ receives path switch request519.

In step 522, MME 116′″ generates and transmits a DNS request to resolvethe SGW information of the Tracking Area Identifier [TAI?] 523 to DNS115′, which is received in step 524 by DNS 115′ of service providerdatacenter 102′″. In step 526, DNS 115′ generates and transmits a DNSrequest to resolve the SGW information of the Tracking Area Identifier[SGW-TAI?] 527 to DNS 2 126′″, which is received in step 528 by DNS 2126′″. In step 530, DNS 115′″ generates and transmits a DNS request toresolve the SGW information of the Tracking Area Identifier [SGW-TAI?]531 to DNS 1 118′″, which is received in step 432 by DNS 1 118″. In someembodiments, DNS request 527 and DNS request 531 communicate the samemessage via a broadcast message intended for a plurality of DNS servers,which may be located a plurality of datacenters.

In step 534, DNS 2 126′″ generates and transmits a DNS response 535 toDNS 115′″, which is received in step 536. In step 537, DNS 1 118′″generates and transmits DNS response 539 to DNS 115′, which is receivedin step 538.

In one embodiment, both DNS response messages (535, 539) communicateIP2, which is the IP address corresponding to data center 2 106′.

In another embodiment, message 535 communicates IP1, which is the IPaddress corresponding to data center 2, and further communicates anindication of high priority; message 537 communicates IP, which is theIP address corresponding to data center 1, and further communicates anindication of low priority.

In step 542, DNS 115′ generates and transmits DNS response 543 to MME116′″, which is received in step 544. In some embodiments, informationincluded in message 543 includes information aggregated from receivedmessage 539 and message 539.

In step 546, MME 116′″ generates and transmits create session request547 to SGW 2 130′, which is received in step 548. In step 550 SGW 130′generates and transmits modify session request 551 to PGW 112′″, whichis received in step 452. In step 554, PGW 112′″ generates and transmitsmodify session response 555 to SGW 2 130′″, which is received in step556. In step 558 SGW 2 130′″ generates and transmits create sessionresponse 559 to MME 116′″, which is received in step 560. In step 562,MME 116′″ generates and transmits path switch request acknowledgments563 to HGW 2 132′, which is received in step 564. In step 566, HGW 2132′″ generates and transmits path switch request acknowledgment 567 toHeNB 108′″, which is received in step 568. In step 574, HeNB 108′″generates and transmits UE context release request 575 to HGW 1 124′″,which may be, and sometimes is, received in step 576. UE context releaserequest 575 is sent in response to receiving path switch requestacknowledgment.

In step 570 MME 116′″ generates and transmits delete session request571, which is, received by SGW 1 112′″ in step 572.

In step 578, SGW 1 122′″ generates and transmits delete session response579 to MME 116′″ which is received in step 580, by MME 116′″.

FIG. 6 is a flowchart 600 of an exemplary communications method inaccordance with various embodiments. Operation of the exemplary methodstarts in step 602 and proceeds to step 604. In step 604, a primarygateway connection between an access point, e.g., HeNB 108, and aprimary gateway, e.g., HGW 1 124, is established. In some embodiments,the primary gateway connection is, e.g., a transport layer connection.In some such embodiments, logical connections are then created for eachUE as needed. Operation proceeds from step 604 to step 606. In step 606,a secondary gateway connection between the access point and a secondarygateway, e.g., HGW 2 132, is established. In some embodiments, thesecondary gateway connection is, e.g., a transport layer connection.Operation proceeds from step 606 to step 608. In step 608, a connectionis established for a user equipment (UE) device, e.g., UE 134, to theaccess point, the established connection being between the UE device andthe access point. In some embodiments, establishing a connection for aUE device to an access point, will trigger establishment of a logicalconnection for the UE device over the primary transport layerconnection. Operation proceeds from step 608 to step 610.

In step 610, primary gateway communications are monitored, e.g., by theaccess point. Step 610 may, and sometimes does, include step 612, inwhich a primary gateway communications failure is detected at the accesspoint. The detected primary gateway communications failure is, e.g., afailure to receive an expected heartbeat or response to a communication.Operation proceeds from step 612 to step 614.

In step 614 the access point transmits a path switch request via thesecondary gateway connection, e.g., a transport layer connection,between the access point and the secondary gateway, to a network entity,e.g., to a mobility management entity (MME), e.g., MME 116, via thesecondary connection and secondary gateway, for the UE device connectedto access point while the UE device remains connected to the accesspoint. In some embodiments, the path switch request will update thecontrol signaling path and the data signaling path for the UE to thesecondary connection thereby moving the control signaling path and thedata signaling path from a first data center to a second data center. Invarious embodiments, the UE device is unaffected by this operation, andthis activity is transparent to the UE.

In some embodiments, the access point, e.g., HeNB 108, is an LTE HeNB.In various embodiments, the path switch request is a request to updatedata and signaling paths corresponding to the UE device. In someembodiments, the path switch request is an LTE S1AP Path Switch Request.In various embodiments, the UE is connected to one cell of said accesspoint prior to and subsequent to the path switch request.

The path switch request is sent via the secondary gateway, e.g., HGW 2132, in response to detecting the primary gateway communicationsfailure.

Operation proceeds from step 614 to one or both of steps 616 and 618.

In optional step 616 the access point transmits a context releaserequest for said UE device to the primary gateway following transmissionof said path switch request. In various embodiments, this will clean upcontext at the first data center, assuming the primary gateway is stillreachable.

Primary gateway, e.g., HGW 1 124, is located at a first data center,e.g., datacenter 1 104. In step 618 a DNS server, e.g., DNS 2 126,receives a request to resolve a name corresponding to a tracking areaidentifier corresponding to the area in which the access point islocated. In various embodiments, the DNS server, e.g., DNS 2 126, islocated at a second data center, e.g., datacenter 2 106, which is anon-failed data center. Operation proceeds from step 618 to step 620. Instep 620 the DNS server responds to the request to resolve the name withan IP address or a domain name and an IP address corresponding to asecond data center which is different from the first data center. Forexample, DNS 2 126 returns IP2 corresponding to the second data center,while DNS 1 118 would have returned IP1 corresponding to the first datacenter, if there was not a first data center failure. Step 620 includesstep 622, in which the DNS server sends a priority indicator indicatingthat the response has a lower priority than a response that may beprovide by a primary DNS server, e.g., DNS 1 118. The secondary DNSserver is responding but has lower priority than the primary DNS server;but the primary data center and/or primary DNS server has failed;therefore, the secondary DNS server will be the only responder and willprevail.

Operation proceeds from step 620 to step 624, in which the access pointreceives a response to the path switch request from the network securityentity, e.g., MME, via the secondary gateway connection.

In some embodiments, operation proceeds from step 624 to optional step626, in which the access point sends, in response to receiving the pathswitch request response, a UE context release message for the UE overthe primary connection to the primary gateway. In various embodiments,this will clean up context at the first data center, assuming theprimary gateway is still reachable.

In various embodiments, the primary DNS server, e.g., DNS 1 118, islocated at the first data center, e.g., data center 1 104. In someembodiments, the first and second data centers (104, 106) correspond todifferent sets of physical equipment. In some such embodiments, thefirst and second data centers (104, 106) are located in differentbuildings.

FIG. 7 is a flowchart 700 of an exemplary communications method inaccordance with various embodiments. Operation of the exemplary methodstarts in step 702 and proceeds to step 704. In step 704, a primarygateway connection between an access point, e.g., HeNB 108′, and aprimary gateway, e.g., HGW 1 124′, is established. In some embodiments,the primary gateway connection is, e.g., a transport layer connection.In some such embodiments, logical connections are then created for eachUE as needed. Operation proceeds from step 704 to step 706. In step 706,a secondary gateway connection between the access point and a secondarygateway, e.g., HGW 2 132′, is established. In some embodiments, thesecondary gateway connection is, e.g., a transport layer connection.Operation proceeds from step 706 to step 708. In step 708, a connectionis established for a user equipment (UE) device, e.g., UE 1 134′, to theaccess point, the established connection being between the UE device andthe access point. In some embodiments, establishing a connection for aUE device to an access point, will trigger establishment of a logicalconnection for the UE device over the primary transport layerconnection. Operation proceeds from step 708 to step 710.

In step 710, primary gateway communications are monitored, e.g., bymanagement device 125′. Step 710 may, and sometimes does, include step712, in which a primary gateway communications failure is detected bythe management device. The detected primary gateway communicationsfailure is, e.g., a failure to receive an expected heartbeat or failureto receive a response to a communication or an failure internal to thegateway, e.g., which has been detected by built in test equipment.Operation proceeds from step 712 to step 713. In step 713 the managementdevice transmits to said access point a failure notification message.Operation proceeds from step 713 to step 714.

In step 714 the access point transmits a path switch request via thesecondary gateway connection, e.g., a transport layer connection,between the access point and the secondary gateway, to a network entity,e.g., to a mobility management entity (MME), e.g., MME 116′, via thesecondary connection and secondary gateway, for the UE device connectedto access point while the UE device remains connected to the accesspoint. In some embodiments, the path switch request will update thecontrol signaling path and the data signaling path for the UE to thesecondary connection thereby moving the control signaling path and thedata signaling path from a first data center to a second data center. Invarious embodiments, the UE device is unaffected by this operation, andthis activity is transparent to the UE.

In some embodiments, the access point, e.g., HeNB 108′, is an LTE HeNB.In various embodiments, the path switch request is a request to updatedata and signaling paths corresponding to the UE device. In someembodiments, the path switch request is an LTE S1AP Path Switch Request.In various embodiments, the UE is connected to one cell of said accesspoint prior to and subsequent to the path switch request.

The path switch request is sent via the secondary gateway, e.g., HGW 2132′, in response to detecting the primary gateway communicationsfailure.

Operation proceeds from step 714 to one or both of steps 716 and 718.

In optional step 716 the access point transmits a context releaserequest for said UE device to the primary gateway following transmissionof said path switch request. In various embodiments, this will clean upcontext at the first data center, assuming the primary gateway is stillreachable.

Primary gateway, e.g., HGW 1 124′, is located at a first data center,e.g., datacenter 1 104′. In step 718 a DNS server, e.g., DNS 2 126′,receives a request to resolve a name corresponding to a tracking areaidentifier corresponding to the area in which the access point islocated. In various embodiments, the DNS server, e.g., DNS 2 126′, islocated at a second data center, e.g., datacenter 2 106′, which is anon-failed data center. Operation proceeds from step 718 to step 720. Instep 720 the DNS server responds to the request to resolve the name withan IP address or a domain name and an IP address corresponding to asecond data center which is different from the first data center. Forexample, DNS 2 126′ returns IP2 corresponding to the second data center,while DNS 1 118′ would have returned IP1 corresponding to the first datacenter, if there was not a first data center failure. Step 720 includesstep 722, in which the DNS server sends a priority indicator indicatingthat the response has a lower priority than a response that may beprovide by a primary DNS server, e.g., DNS 1 118′. The secondary DNSserver is responding but has lower priority than the primary DNS server;but the primary data center and/or primary DNS server has failed;therefore, the secondary DNS server will be the only responder and willprevail.

Operation proceeds from step 720 to step 724, in which the access pointreceives a response to the path switch request from the network securityentity, e.g., MME, via the secondary gateway connection.

In some embodiments, operation proceeds from step 724 to optional step726, in which the access point sends, in response to receiving the pathswitch request response, a UE context release message for the UE overthe primary connection to the primary gateway. In various embodiments,this will clean up context at the first data center, assuming theprimary gateway is still reachable.

In various embodiments, the primary DNS server, e.g., DNS 1 118′, islocated at the first data center, e.g., data center 1 104′. In someembodiments, the first and second data centers (104′, 106′) correspondto different sets of physical equipment. In some such embodiments, thefirst and second data centers (104′, 106′) are located in differentbuildings.

FIG. 8 is a flowchart 800 of an exemplary communications method inaccordance with various embodiments. Operation of the exemplary methodstarts in step 802 and proceeds to step 804. In step 804, a primarygateway connection between an access point, e.g., HeNB 108″, and aprimary gateway, e.g., HGW 1 124″, is established. In some embodiments,the primary gateway connection is, e.g., a transport layer connection.In some such embodiments, logical connections are then created for eachUE as needed. Operation proceeds from step 804 to step 806. In step 806,a secondary gateway connection between the access point and a secondarygateway, e.g., HGW 2 132″, is established. In some embodiments, thesecondary gateway connection is, e.g., a transport layer connection.Operation proceeds from step 806 to step 808. In step 808, a connectionis established for a user equipment (UE) device, e.g., UE 1 134″, to theaccess point, the established connection being between the UE device andthe access point. In some embodiments, establishing a connection for aUE device to an access point, will trigger establishment of a logicalconnection for the UE device over the primary transport layerconnection. Operation proceeds from step 808 to step 810.

In step 810, primary gateway communications are monitored, e.g., bymanagement device 125″. Step 810 may, and sometimes does, include step812, in which a primary gateway communications failure is detected bythe management device. The detected primary gateway communicationsfailure is, e.g., a failure to receive an expected heartbeat or failureto receive a response to a communication or an failure internal to thegateway, e.g., which has been detected by built in test equipment.Operation proceeds from step 812 to step 814

In step 814 the management device is operated to communicate a dynamicDNS update for a tracking area identifier corresponding to a location ofthe access point, said dynamic DNS update including an IP address or adomain name corresponding to a second data center, e.g. IP2, orDomainName2, corresponding to datacenter 2 106″, which is different thanthe IP address or domain name corresponding to the first datacenter,e.g., IP1, or DomainName1, corresponding to datacenter 1 104″. Thedynamic DNS update is communicated to one or more DNSs, e.g., changingthe stored IP address or domain name corresponding to the tracking areain which HeNB 108″ is located from IP1 or DomainName1, which correspondsto datacenter 1, to IP2 or DomainName2, which corresponds to datacenter2. Thus, in some embodiments, in step 814 the management devicecommunicates the dynamic DNS update in response to detection of firstdata center fault condition. Operation proceeds from step 814 to step816.

In step 816 the management device transmits to said access point afailure notification message. Operation proceeds from step 816 to step818.

In step 818 the access point transmits a path switch request via thesecondary gateway connection, e.g., a transport layer connection,between the access point and the secondary gateway, to a network entity,e.g., to a mobility management entity (MME), e.g., MME 116″, via thesecondary connection and secondary gateway, for the UE device connectedto access point while the UE device remains connected to the accesspoint. In some embodiments, the path switch request will update thecontrol signaling path and the data signaling path for the UE to thesecondary connection thereby moving the control signaling path and thedata signaling path from a first data center to a second data center. Invarious embodiments, the UE device is unaffected by this operation, andthis activity is transparent to the UE.

In some embodiments, the access point, e.g., HeNB 108″, is an LTE HeNB.In various embodiments, the path switch request is a request to updatedata and signaling paths corresponding to the UE device. In someembodiments, the path switch request is an LTE S1AP Path Switch Request.In various embodiments, the UE is connected to one cell of said accesspoint prior to and subsequent to the path switch request.

The path switch request is sent via the secondary gateway, e.g., HGW 2132″, in response to detecting the primary gateway communicationsfailure.

Operation proceeds from step 818 to one or both of steps 820 and 822.

In optional step 820 the access point transmits a context releaserequest for said UE device to the primary gateway following transmissionof said path switch request. In various embodiments, this will clean upcontext at the first data center, assuming the primary gateway is stillreachable.

Primary gateway, e.g., HGW 1 124″, is located at a first data center,e.g., datacenter 1 104″. In step 822 a DNS server, e.g., DNS 2 126″,receives a request to resolve a name corresponding to a tracking areaidentifier corresponding to the area in which the access point islocated. In various embodiments, the DNS server, e.g., DNS 2 126″, islocated at a second data center, e.g., datacenter 2 106″, which is anon-failed data center. Operation proceeds from step 822 to step 824. Instep 824 the DNS server responds to the request to resolve the name withan IP address or a domain name and an IP address corresponding to asecond data center which is different from the first data center. Forexample, DNS 2 126″ returns IP2, or DomainName2 and IP2, correspondingto the second data center, based on the updated information communicatedin step 814.

Operation proceeds from step 824 to step 826, in which the access pointreceives a response to the path switch request from the network securityentity, e.g., MME 116″, via the secondary gateway connection.

In some embodiments, operation proceeds from step 826 to optional step828, in which the access point sends, in response to receiving the pathswitch request response, a UE context release message for the UE overthe primary connection to the primary gateway. In various embodiments,this will clean up context at the first data center, assuming theprimary gateway is still reachable.

In various embodiments, the primary DNS server, e.g., DNS 1 118″, islocated at the first data center, e.g., data center 1 104″. In someembodiments, the first and second data centers (104″, 106″) correspondto different sets of physical equipment. In some such embodiments, thefirst and second data centers (104″, 106″) are located in differentbuildings.

FIG. 9 is a flowchart 900 of an exemplary communications method inaccordance with various embodiments. Operation of the exemplary methodstarts in step 902 and proceeds to step 904. In step 904, a primarygateway connection between an access point, e.g., HeNB 108′″, and aprimary gateway, e.g., HGW 1 124′″, is established. In some embodiments,the primary gateway connection is, e.g., a transport layer connection.In some such embodiments, logical connections are then created for eachUE as needed. Operation proceeds from step 904 to step 906. In step 906,a secondary gateway connection between the access point and a secondarygateway, e.g., HGW 2 132′″, is established. In some embodiments, thesecondary gateway connection is, e.g., a transport layer connection.Operation proceeds from step 906 to step 908. In step 908, a connectionis established for a user equipment (UE) device, e.g., UE 1 134′″, tothe access point, the established connection being between the UE deviceand the access point. In some embodiments, establishing a connection fora UE device to an access point, will trigger establishment of a logicalconnection for the UE device over the primary transport layerconnection. Operation proceeds from step 908 to step 910.

In step 910, a management device, e.g., management device 125′″,determines that a scheduled maintenance operation is to be performed onthe first data center. Operation proceeds from step 910 to step 912.

In step 912 the management device is operated to communicate a dynamicDNS update for a tracking area identifier corresponding to a location ofthe access point, said dynamic DNS update including an IP address or adomain name corresponding to a second data center, e.g. IP2, orDomainName2, corresponding to datacenter 2 106′″, which is differentthan the IP address or domain name corresponding to the firstdatacenter, e.g., IP1, or DomainName1, corresponding to datacenter 1104′″. The dynamic DNS update is communicated to one or more DNSs, e.g.,changing the stored IP address corresponding to the tracking area inwhich HeNB 108′″ is located from IP1 or DomainName1, which correspondsto datacenter 1, to IP2 or DomainName2, which corresponds to datacenter2. Thus, in some embodiments, the management device communicates thedynamic DNS update in response in accordance with a scheduledmaintenance operation on the first data center. Operation proceeds fromstep 912 to step 914.

In step 914 the management device transmits to said access point amaintenance notification message. Operation proceeds from step 914 tostep 916.

In step 916 the access point transmits a path switch request via thesecondary gateway connection, e.g., a transport layer connection,between the access point and the secondary gateway, to a network entity,e.g., to a mobility management entity (MME), e.g., MME 116′″, via thesecondary connection and secondary gateway, for the UE device connectedto access point while the UE device remains connected to the accesspoint. In some embodiments, the path switch request will update thecontrol signaling path and the data signaling path for the UE to thesecondary connection thereby moving the control signaling path and thedata signaling path from a first data center to a second data center. Invarious embodiments, the UE device is unaffected by this operation, andthis activity is transparent to the UE.

In some embodiments, the access point, e.g., HeNB 108′″, is an LTE HeNB.In various embodiments, the path switch request is a request to updatedata and signaling paths corresponding to the UE device. In someembodiments, the path switch request is an LTE S1AP Path Switch Request.In various embodiments, the UE is connected to one cell of said accesspoint prior to and subsequent to the path switch request.

Operation proceeds from step 916 to one or both of steps 918 and 920.

In optional step 918 the access point transmits a context releaserequest for said UE device to the primary gateway following transmissionof said path switch request. In various embodiments, this will clean upcontext at the first data center, assuming the primary gateway is stillreachable.

Primary gateway, e.g., HGW 1 124′″, is located at a first data center,e.g., datacenter 1 104′. In step 920 a DNS server, e.g., DNS 2 126′″,receives a request to resolve a name corresponding to a tracking areaidentifier corresponding to the area in which the access point islocated. In various embodiments, the DNS server, e.g., DNS 2 126′″, islocated at a second data center, e.g., datacenter 2 106′″, which is anon-failed data center which is to remain active while data center 1 isundergoing maintenance. Operation proceeds from step 920 to step 922. Instep 922 the DNS server responds to the request to resolve the name withan IP address or a domain name and an IP address corresponding to asecond data center which is different from the first data center. Forexample, DNS 2 126′″ returns IP2, or DomainName2 and IP2, correspondingto the second data center, based on the updated information communicatedin step 912.

Operation proceeds from step 922 to step 924, in which the access pointreceives a response to the path switch request from the network securityentity, e.g., MME 116′″, via the secondary gateway connection.

In some embodiments, operation proceeds from step 924 to optional step926, in which the access point sends, in response to receiving the pathswitch request response, a UE context release message for the UE overthe primary connection to the primary gateway. In various embodiments,this will clean up context at the first data center, assuming theprimary gateway is still reachable.

In various embodiments, the primary DNS server, e.g., DNS 1 118′″, islocated at the first data center, e.g., data center 1 104′″. In someembodiments, the first and second data centers (104′″, 106′″) correspondto different sets of physical equipment. In some such embodiments, thefirst and second data centers (104′″, 106′″) are located in differentbuildings.

FIG. 10 is a flowchart 1000 of an exemplary communications method inaccordance with various embodiments. Operation of the exemplary methodstarts in step 1002 and proceeds to step 1004. In step 1004, a primarygateway connection between an access point, e.g., HeNB 108′″, and aprimary gateway, e.g., HGW 1 124′″, is established. In some embodiments,the primary gateway connection is, e.g., a transport layer connection.In some such embodiments, logical connections are then created for eachUE as needed. Operation proceeds from step 1004 to step 1006. In step1006, a secondary gateway connection between the access point and asecondary gateway, e.g., HGW 2 132′″, is established. In someembodiments, the secondary gateway connection is, e.g., a transportlayer connection. Operation proceeds from step 1006 to step 1008. Instep 1008, a connection is established for a user equipment (UE) device,e.g., UE 1 134′″, to the access point, the established connection beingbetween the UE device and the access point. In some embodiments,establishing a connection for a UE device to an access point, willtrigger establishment of a logical connection for the UE device over theprimary transport layer connection. Operation proceeds from step 1008 tostep 1010.

In step 1010, a management device, e.g., management device 125′″,determines that a scheduled maintenance operation is to be performed onthe first data center. Operation proceeds from step 1010 to step 1012and step 1013.

In step 1012 the management device is operated to communicate a dynamicDNS update for a tracking area identifier corresponding to a location ofthe access point, said dynamic DNS update including a first priorityindicator which decreases the priority of a response that may beprovided by the primary DNS server. In step 1013 the management deviceis operated to communicate a dynamic DNS update for a tracking areaidentifier corresponding to a location of the access point, said dynamicDNS update including a second priority indicator which increase thepriority of a response that may be provided by the secondary DNS server.For example, in one embodiment, prior to the update, for the trackingarea in which HeNB 108′″ is located: DNS 1 maps the tracking areaidentifier value to IP1, which corresponds to datacenter 1, with anassociated high priority value; and DNS 2 maps to IP2, which correspondsto datacenter 2, with a low priority value. Continuing with the example,after the update, for the tracking area in which HeNB 108′″ is located:DNS 1 maps the tracking area identifier value to IP1, which correspondsto datacenter 1, with an associated low priority value; and DNS 2 mapsto IP2, which corresponds to datacenter 2, with a high priority value.Thus, in some embodiments, the management device communicates thedynamic DNS update in response in accordance with a scheduledmaintenance operation on the first data center. Operation proceeds fromstep 1012 and 1013 to step 1014.

In step 1014 the management device transmits to said access point amaintenance notification message. Operation proceeds from step 1014 tostep 1016.

In step 1016 the access point transmits a path switch request via thesecondary gateway connection, e.g., a transport layer connection,between the access point and the secondary gateway, to a network entity,e.g., to a mobility management entity (MME), e.g., MME 116′, via thesecondary connection and secondary gateway, for the UE device connectedto access point while the UE device remains connected to the accesspoint. In some embodiments, the path switch request will update thecontrol signaling path and the data signaling path for the UE to thesecondary connection thereby moving the control signaling path and thedata signaling path from a first data center to a second data center. Invarious embodiments, the UE device is unaffected by this operation, andthis activity is transparent to the UE.

In some embodiments, the access point, e.g., HeNB 108′″, is an LTE HeNB.In various embodiments, the path switch request is a request to updatedata and signaling paths corresponding to the UE device. In someembodiments, the path switch request is an LTE S1AP Path Switch Request.In various embodiments, the UE is connected to one cell of said accesspoint prior to and subsequent to the path switch request.

Operation proceeds from step 1016 to one or both of steps 1018 and 1020.

In optional step 1018 the access point transmits a context releaserequest for said UE device to the primary gateway following transmissionof said path switch request. In various embodiments, this will clean upcontext at the first data center, assuming the primary gateway is stillreachable.

Primary gateway, e.g., HGW 1 124′″, is located at a first data center,e.g., datacenter 1 104″. In step 1020 a DNS server, e.g., DNS 2 126′″,receives a request to resolve a name corresponding to a tracking areaidentifier corresponding to the area in which the access point islocated. In various embodiments, the DNS server, e.g., DNS 2 126′″, islocated at a second data center, e.g., datacenter 2 106′″, which is anon-failed data center which is to remain active while data center 1 isundergoing maintenance. Operation proceeds from step 1020 to step 1022.

In step 1022 the DNS server responds to the request to resolve the namewith an IP address or a domain name and an IP address corresponding to asecond data center which is different from the first data center. Forexample, DNS 2 126′″ returns IP2 corresponding to the second datacenter. Note that the DNS updates of steps 1012 and 1013 has switchedpriority so that a response from DNS 2 will have higher priority than aresponse from DNS 1, and the data center will be switched from datacenter 1 to data center 2.

Operation proceeds from step 1022 to step 1024, in which the accesspoint receives a response to the path switch request from the networksecurity entity, e.g., MME 116′″, via the secondary gateway connection.

In some embodiments, operation proceeds from step 1024 to optional step1026, in which the access point sends, in response to receiving the pathswitch request response, a UE context release message for the UE overthe primary connection to the primary gateway. In various embodiments,this will clean up context at the first data center, assuming theprimary gateway is still reachable.

In various embodiments, the primary DNS server, e.g., DNS 1 118′″, islocated at the first data center, e.g., data center 1 104′″. In someembodiments, the first and second data centers (104′″, 106′″) correspondto different sets of physical equipment. In some such embodiments, thefirst and second data centers (104′″, 106′″) are located in differentbuildings.

FIG. 11 is a drawing illustrating exemplary mapping tables which may beincluded in exemplary DNSs in accordance with an exemplary embodiment.Tables (1100, 1102, 1104) are DNS mapping table for DNS 1, e.g., DNS 1118 or DNS 1 118′. Table 1100 maps a tracking area identifier to atracking area identifier (TAI) domain name. Table 1102 maps a TAI domainname to a SGW domain name and a priority indicator value. Table 1104maps a SGW domain name to a SGW IP address. Tables (1150, 1152, 1154)are DNS mapping table for DNS 2, e.g., DNS 2 126 or DNS 2 126′. Table1150 maps a tracking area identifier to a tracking area identifier (TAI)domain name. Table 1152 maps a TAI domain name to a SGW domain name anda priority indicator value. Table 1154 maps a SGW domain name to a SGWIP address. In this embodiment, different DNSs map the same trackingarea identifier value to different SGW domain names and differentpriority indicator values, and the different SGW domain names map todifferent IP addresses.

For DNS 1, tracking area identifier value=TAIVALUE1, maps to TAI domainname=TAIDN1, which maps to SGW domain name=DomainName1 and priorityindicator value=1, which indicates high priority; SGW domainname=DomainName1 maps to IP address=IP1, which corresponds to datacenter 1. For DNS 2, tracking area identifier value=TAIVALUE1, maps toTAI domain name=TAIDN1, which maps to SGW domain name=DomainName2 andpriority indicator value=2, which indicates low priority; SGW domainname=DomainName2 maps to IP address=IP2, which corresponds to datacenter 2. Thus for an access point, e.g., HeNB 108, located in trackingarea 1, data center 1 is the primary data center, and data center 2 isthe secondary or back-up data center.

For DNS 1, tracking area identifier value=TAIVALUE2 maps to TAI domainname=TAIDN2, which maps to SGW domain name=DomainName1 and priorityindicator value=2 which indicates low priority; SGW domainname=DomainName1 maps to IP address=IP1, which corresponds to datacenter 1. For DNS 2, tracking area identifier value=TAIVALUE2 maps toTAI domain name=TAIDN2, which maps to SGW domain name=DomainName2 andpriority indicator value=1, which indicates high priority; SGW domainname=DomainName2 maps to IP address=IP2, which corresponds to datacenter 2. Thus for an access point, e.g., HeNB N 110, located intracking area 2, data center 2 is the primary data center, and datacenter 1 is the secondary or back-up data center.

FIG. 12 is a drawing illustrating exemplary original and updated mappingtables which may be included in exemplary DNSs in accordance withanother exemplary embodiment. Set of tables 1200, including table 1202,table 1204, and table 1206, is an original, e.g. pre-update, set of DNSmapping tables for DNS 1, e.g., DNS 1 118″ or DNS 1 118′″ and/or for DNS2, e.g., DNS 2 126″ or DNS 2 126′″. Table 1202 maps tracking areaidentifier to TAI domain name; table 1204 maps TAI domain name to SGWdomain name; and table 1206 maps SGW domain name to SGW IP address.

Set of tables 1201, including table 1202′, 1204′, and 1206′, is anupdated set of DNS mapping tables for DNS 1, e.g., DNS 1 118″ or DNS 1118′″, e.g., following a communicated dynamic DNS update message frommanagement device 125″ or 125′″ and/or for DNS 2, e.g., DNS 2 126″ orDNS 2 126′″, e.g., following a communicated dynamic DNS update messagefrom management device 125″ or 125′″.

In this embodiment, at a given time, each of the DNSs map the sametracking area identifier value to the same IP address. However, the IPaddress can be, and sometimes is, dynamically updated over time, e.g.,in response to a detected fault condition or scheduled maintenance.

Originally, tracking area identifier value=TAIVALUE1 maps to TAI domainname=TAIDN1, which maps to SGW domain name=DomainName1, which maps to IPaddress=IP1, which corresponds to data center 1; and tracking areaidentifier value=TAIVALUE2 maps to TAI domain name=TAIDN2, which maps toSGW Domain Name=DomainName2, which maps to IP address=IP2, whichcorresponds to data center 2.

In this example, the dynamic DNS update changes the mapping between anSGW domain name and an SGW IP address. Table entry 1208 of table 1206indicates IP1, while table entry 1208′ of table 1206′ indicates IP2.

In this example, after the update, tracking area identifiervalue=TAIVALUE1 maps to TAIDN1, which maps to SGW DomainName=DomainName1, which maps to IP address=IP2, which corresponds todata center 2; and tracking area identifier value=TAIVALUE 2 maps to TAIdomain name=TAIDN2, which maps to SGW Domain Name=DomainName2, whichmaps to IP address=IP2, which corresponds to data center 2.

In this example, consider that access point HeNB 108″ or 108′″ islocated in the tracking area with tracking area identifiervalue=TAIVALUE1 and that a detected primary gateway communicationsfailure or scheduled maintenance on data center 1 104″ or 104′″ is thetrigger event for transition from datacenter 1 104″ or 104′″ todatacenter 2 106″ or 106′″.

FIG. 12A is a drawing illustrating exemplary original and updatedmapping tables which may be included in exemplary DNSs in accordancewith yet another exemplary embodiment. Set of tables 1250, includingtable 1252, table 1254, and table 1256, is an original, e.g. pre-update,set of DNS mapping tables for DNS 1, e.g., DNS 1 118″ or DNS 1 118′″and/or for DNS 2 e.g., DNS 2 126″ or DNS 2 126′″. Table 1252 mapstracking area identifier to TAI domain name; table 1254 maps TAI domainname to SGW domain name; and table 1256 maps SGW domain name to SGW IPaddress.

Set of tables 1251, including table 1252′, 1254′, and 1256′, is anupdated set of DNS mapping tables for DNS 1, e.g., DNS 1 118″ or DNS 1118′″, e.g., following a communicated dynamic DNS update message frommanagement device 125″ or 125′″ and/or for DNS 2, e.g., DNS 2 126″ orDNS 2 126′″, e.g., following a communicated dynamic DNS update messagefrom management device 125″ or 125′″.

In this exemplary embodiment, at a given time, each of the DNSs map thesame tracking area identifier value to the same domain name. However,the domain name can be, and sometimes is, dynamically updated over time,e.g., in response to a detected fault condition or scheduledmaintenance.

Originally, tracking area identifier value=TAIVALUE1 maps to TAI domainname=TAIDN1, which maps to SGW domain name=DomainName1, which itselfmaps to IP address=IP1, which corresponds to data center 1; and trackingarea identifier value=TAIVALUE2 maps to TAI domain name=TAIDN2, whichmaps to SGW domain name=DomainName2, which itself maps to IPaddress=IP2, which corresponds to data center 2.

In this example, the dynamic DNS update changes the mapping between aTAI domain name and an SGW domain name. Table entry 1258 of table 1254indicates DomainName1, while table entry 1258′ of table 1254′ indicatesDomainName2.

In this example, after the update, tracking area identifiervalue=TAIVALUE1 maps to TAI domain name=TAIDN1, which maps to SGW domainname=DomainName2, which itself maps to IP address=IP2, which correspondsto data center 2; and tracking area identifier value=TAIVALUE2 maps toTAI domain name=TAIDN2, which maps to SGW domain name=DomainName2, whichitself maps to IP address=IP2, which corresponds to data center 2.

In this example, consider that access point HeNB 108″ or 108′″ islocated in the tracking area with tracking area identifiervalue=TAIVALUE1 and that a detected primary gateway communicationsfailure or scheduled maintenance on data center 1 104″ or 104′″ is thetrigger event for transition from datacenter 1 104″ or 104′″ todatacenter 2 106″ or 106′″.

FIG. 13 is a drawing 1300 illustrating exemplary original mapping tableswhich may be included in exemplary DNSs in accordance with anotherexemplary embodiment. Set of tables 1301, including table 1302, 1304,1306, is a set of original, e.g. pre-update, DNS mapping tables for DNS1, e.g., DNS 1 118″ or DNS 1 118′″. Table 1302 maps tracking areaidentifier to TAI domain name; table 1304 maps TAI domain name to SGWdomain name and priority indicator value; and table 1306 maps SGW domainname to SGW IP address.

Set of tables 1303, including table 1308, 1310, 1312, is a set oforiginal, e.g. pre-update, DNS mapping tables for DNS 2, e.g., DNS 2126″ or DNS 2 126′″. Table 1308 maps tracking area identifier to TAIdomain name; table 1310 maps TAI domain name to SGW domain name andpriority indicator value; and table 1312 maps SGW domain name to SGW IPaddress.

Originally, for DNS 1, tracking area identifier value=TAIVALUE1 maps toTAI domain name=TAIDN1, which maps to SGW domain name=DomainName1 andpriority indicator value=2, which indicates medium priority; SGW domainname=DomainName1 maps to IP address=IP1, which corresponds to datacenter 1. Also, originally for DNS1, tracking area identifiervalue=TAIVALUE2 maps to TAI domain name=TAIDN2, which maps to SGW domainname=DomainName1 and priority indicator value=3, which indicates lowpriority; SGW domain name=DomainName1 maps to IP address=IP1, whichcorresponds to data center 1.

Originally, for DNS 2, tracking area identifier value=TAIVALUE1 maps toTAI domain name=TAIDN1, which maps to SGW domain name=DomainName2 andpriority indicator value=3, which indicates low priority; SGW domainname=DomainName 2 maps to IP address=IP2, which corresponds to datacenter 2. Also originally for DNS 2, tracking area identifiervalue=TAIVALUE2 maps to TAIDN2, which maps to SGW domainname=DomainName2 and priority indicator value=2, which indicates mediumpriority; SGW domain name=DomainName 2 maps to IP address=IP2, whichcorresponds to data center 2.

FIG. 13A is a drawing 1300′ illustrating exemplary updated mappingtables which may be included in exemplary DNSs in accordance with theanother exemplary embodiment. Set of table 1301′, including tables1302′, 1304′ and 1306′, is an updated set DNS mapping tables for DNS 1,e.g., DNS 1 118″ or DNS 1 118′″, e.g., following a communicated dynamicDNS update message from management device 125″ or 125′″. Table 1302′maps tracking area identifier to TAI domain name; table 1304′ maps TAIdomain name to SGW domain name and priority indicator value; and table1306′ maps SGW domain name to SGW IP address.

Set of tables 1303′, including table 1308′, 1310′ and 1312′. is anupdated set DNS mapping tables for DNS 2, e.g., DNS 2 126″ or DNS 2126′″, e.g., following a communicated dynamic DNS update message frommanagement device 125″ or 125′″. Table 1308′ maps tracking areaidentifier to TAI domain name; table 1310′ maps TAI domain name to SGWdomain name and priority indicator value; and table 1312′ maps SGWdomain name to SGW IP address.

In this example after the update, for DNS 1, tracking area identifiervalue=TAIVALUE1 maps to TAI domain name=TAIDN1, which maps to SGW domainname=DomainName1 and priority indicator value=3 which indicates lowpriority; SGW domain name=DomainName1 maps to IP address=IP1, whichcorresponds to data center 1. Also, in this example after the update forDNS1, tracking area identifier value=TAIVALUE2 maps to TAI domainname=TAIDN2, which maps to SGW domain name=DomainName1 and priorityindicator value=3, which indicates low priority; SGW domainname=DomainName1 maps to IP address=IP1, which corresponds to datacenter 1.

In this example after the update, for DNS 2, tracking area identifiervalue=TAIVALUE1 maps to TAI domain name=TAIDN1, which maps to SGW domainname=DomainName2 and priority indicator value=1, which indicates highpriority; SGW domain name=DomainName 2 maps to IP address=IP2, whichcorresponds to data center 2. Also in this example after the update forDNS 2, tracking area identifier value=TAIVALUE2 maps to TAIDN2, whichmaps to SGW domain name=DomainName2 and priority indicator value=2,which indicates medium priority; SGW domain name=DomainName 2 maps to IPaddress=IP2, which corresponds to data center 2.

In this embodiment, each of the DNSs map the same tracking areaidentifier value to different IP addresses. However, the priority canbe, and sometimes is, dynamically updated over time, e.g., in responseto a detected fault condition or scheduled maintenance.

In this example, consider that access point HeNB 108″ or 108′″ islocated in the tracking area with tracking area identifiervalue=TAIVALUE1 and that a detected primary gateway communicationsfailure or scheduled maintenance on data center 1 104″ or 104′″ is thetrigger event for transition from datacenter 1 104″ or 104′″ todatacenter 2 106″ or 106′″. A dynamic change in stored priorityinformation in the DNS mapping tables is utilized to cause redirectionto datacenter 2 106″ or 106′″, when a path switch request issubsequently sent from the access point HeNB 108″ or 108′″.

In particular with regard to the DNS 1 mapping tables, table entry 1314of table 1304 indicates priority indicator value=2, which indicatesmedium priority; and table entry 1314′ of table 1304′ indicates priorityindicator value=3, which indicates low priority. And with regard to theDNS 2 mapping tables, table entry 1316 of table 1310 indicates priorityindicator value=3, which indicates low priority; and table entry 1316′of table 1310′ indicates priority indicator value=1, which indicateshigh priority.

FIG. 14 is a drawing of an exemplary access point 1400, e.g., a HeNB, inaccordance with an exemplary embodiment. Exemplary access point 1400 is,e.g., HeNB 108 of system 100 of FIG. 1 or FIG. 2, HeNB 108′ of FIG. 3,HeNB 108″ of FIG. 4, HeNB 108′″ of FIG. 5, and/or an access pointimplementing steps of the one or more of the methods of FIG. 6-10.

Access point 1400, e.g., a HeNB, includes a processor 1402, e.g., a CPU,memory 1404, and an assembly of modules 1410, e.g., an assembly ofhardware modules, coupled together via a bus 1409 over which the variouselements may exchange data and information. Access point 1400 furtherincludes an input module 1406 and an output module 1408, which arecoupled to the processor 1402. In various the input module 1406 and theoutput module 1408 are included as part of a communications interfacemodule 1415. In various embodiments, communications interface module1415 includes interfaces for communications with different types ofdevices, e.g., HGWs, UEs, SGWs, a PGWs, DNSs, MMEs, management devices,etc. and/or supporting a plurality of different communicationsprotocols. The input module 1406 and/or output module 1408 may, and insome embodiments do, include a plurality of different ports and/orinterfaces. Input module 1406 includes a plurality of receiversincluding a first receiver RX 1 1418 and a second receiver RX 2 1420,which is a wireless receiver. Output module 1408 includes a plurality oftransmitters including a first transmitter TX 1 1422 and a secondtransmitter TX 2 1424, which is a wireless transmitter.

Access point 1400 receives signals including messages via input module1406. Exemplary signals received by receiver RX 1 1418 include primarytransport connection establishment signals, secondary transportconnection establishment signals, path switch request acknowledgmentsignals, fault detection notification messages, and maintenancenotification messages. Exemplary signals received by receiver RX 2include UE connection establishment signals.

Access point 1400 transmits signals including messages via output module1408. Exemplary signals transmitted by transmitter TX 1 1422 includeprimary transport connection establishment signals, secondary transportconnection establishment signals, path switch request signals, and UEcontext release request signals. Exemplary signals transmitted bytransmitter TX 2 1424 include UE connection establishment signals.

Memory 1404 includes routines 1412 and data/information 1414. Routines1412 includes an assembly of modules 1416.

FIG. 15 is a drawing of an assembly of modules 1500 which may beincluded in an exemplary access point, e.g., an exemplary HeNB, inaccordance with an exemplary embodiment. Assembly of modules 1500 whichcan, and in some embodiments is, used in the access point 1400. Themodules in the assembly of modules 1500 can, and in some embodimentsare, implemented fully in hardware within the processor 1402, e.g., asindividual circuits. The modules in the assembly of modules 1500 can,and in some embodiments are, implemented fully in hardware within theassembly of modules 1410, e.g., as individual circuits corresponding tothe different modules. In other embodiments some of the modules areimplemented, e.g., as circuits, within the processor 1402 with othermodules being implemented, e.g., as circuits within assembly of modules1410, external to and coupled to the processor 1402. As should beappreciated the level of integration of modules on the processor and/orwith some modules being external to the processor may be one of designchoice.

Alternatively, rather than being implemented as circuits, all or some ofthe modules may be implemented in software and stored in the memory 1404of the access point 1400, with the modules controlling operation ofaccess point 1400 to implement the functions corresponding to themodules when the modules are executed by a processor, e.g., processor1402. In some such embodiments, the assembly of modules 1500 is includedin the memory 1404 as assembly of modules 1416. In still otherembodiments, various modules in assembly of modules 1500 are implementedas a combination of hardware and software, e.g., with another circuitexternal to the processor providing input to the processor 1402 whichthen under software control operates to perform a portion of a module'sfunction. While shown in the FIG. 14 embodiment as a single processor,e.g., computer, it should be appreciated that the processor 1402 may beimplemented as one or more processors, e.g., computers.

When implemented in software the modules include code, which whenexecuted by the processor 1402, configure the processor 1402 toimplement the function corresponding to the module. In embodiments wherethe assembly of modules 1500 is stored in the memory 1404, the memory1404 is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each module, for causing atleast one computer, e.g., processor 1402, to implement the functions towhich the modules correspond.

Completely hardware based or completely software based modules may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented modules may be used to implementthe functions. As should be appreciated, the modules illustrated in FIG.15 control and/or configure the access point 1400 or elements thereinsuch as the processor 1402, to perform the functions of correspondingsteps illustrated in the method of one or more of the signaling drawingof FIG. 2-5 and/or one or more of the flowcharts of FIGS. 6-10. Thus theassembly of modules 1500 includes various modules that perform functionsof corresponding steps of one or more of FIGS. 2-10.

Assembly of modules 1500 includes a module 1502 configured to establisha primary gateway connection between the access point and a primarygateway, a module 1504 configured to establish a secondary connectionbetween the access point and a secondary gateway, a module 1506configured to establish a connection for a user equipment (UE) device tothe access point, the established connection being between the UE deviceand the access point. Assembly of modules 1500 further includes a module1508 configured to monitor primary gateway communications. Module 1508includes a module 1510 configured to detect at the access point aprimary gateway communications failure, e.g., a failure to receive anexpected heartbeat or response to a communication. Assembly of modules1500 further includes a module 1512 configured to generate a path switchrequest, a module 1514 configured to control the transmitter ti transmita path switch request via the secondary gateway connection between theaccess point and the secondary gateway, to a network entity, for the UEdevice connected to the access point which the UE device remainsconnected to the access point. Assembly of modules 1500 further includesa module 1516 configured to control the transmitter to transmit acontext release request for said UE device to the primary gatewayfollowing transmission of the path switch request, a module 1518configured to receive a response to the path switch request from thenetwork entity via the secondary gateway connection, and a module 1520configured to send, in response to receiving the path switch requestresponse a UE context release message for the UE over the primaryconnection to the primary gateway. In some embodiments, assembly ofmodules 1500 includes one or module 1516 and 1520.

Assembly of modules 1500 further includes a module 1522 configured toreceive a fault notification message, e.g., from a management devicewhich detected a fault condition with the first datacenter. Assembly ofmodules 1500 further includes a module 1524 configured to receive amaintenance notification message, e.g., from a management device whichhas determined a scheduled maintenance operation is to be performed onthe first data center.

In some embodiments, the access point is an LTE HeNB. In someembodiments, the path switch request is an request to update data andsignaling paths corresponding to the UE device. In various embodiments,the path switch request is an LTE S1AP Path Switch Request.

In various embodiments, module 1514 is configured to control thetransmitter to transmit a path switch request in response to module 1510detecting a primary gateway communications fail. In various embodiments,module 1514 is configured to control the transmitter to transmit a pathswitch request in response to module 1522 receiving a fault notificationmessage, e.g., a management device has detected a primary gatewaycommunications fail and sent the fault notification message. In variousembodiments, module 1514 is configured to control the transmitter totransmit a path switch request in response to module 1524 receiving amaintenance notification message.

FIG. 16 is a drawing of an exemplary DNS server 1600, e.g., a secondaryDNS server, in accordance with an exemplary embodiment. Exemplary DNSserver 1600 is, e.g., DNS 2 126 of system 100 of FIG. 1 or FIG. 2, DNS 2126′ of FIG. 3, DNS 2″ of FIG. 4, DNS 2′″ 126′″ of FIG. 5, and/or an DNSimplementing steps of the one or more of the methods of FIG. 6-10.

DNS server 1600, e.g., a secondary DNS server, includes a processor1602, e.g., a CPU, memory 1604, and an assembly of modules 1610, e.g.,an assembly of hardware modules, coupled together via a bus 1611 overwhich the various elements may exchange data and information. DNS server1600 further includes an input module 1606 and an output module 1608,which are coupled to the processor 1602. In various embodiments, theinput module 1606 and the output module 1608 are included as part of acommunications interface module 1615. In various embodiments,communications interface module 1615 includes interfaces forcommunications with different types of devices, e.g., other DNSs, HGWs,SGWs, MMES, HeNBs, management devices, etc. and/or supporting aplurality of different communications protocols. The input module 1606and/or output module 1608 may, and in some embodiments do, include aplurality of different ports and/or interfaces. Input module 1606includes one or more receivers including RX 1607. Output module 1608includes one or more transmitters including a transmitter TX 1609.

DNS server 1600 receives signals including messages via input module1606. Exemplary signals received by receiver RX 1607 include DNS requestmessages, and dynamic DNS update messages.

DNS server 1600 transmits signals including messages via output module1608. Exemplary signals transmitted by transmitter TX 1609 include DNSresponse messages.

Memory 1604 includes routines 1612 and data/information 1614. Routines1612 includes an assembly of modules 1616. Data/information 1614, insome embodiments, includes mapping information, e.g., exemplary mappingtables, such as illustrated in one or more of FIGS. 11-13.

FIG. 17 is a drawing of an assembly of modules 1700 which may beincluded in an exemplary DNS server in accordance with an exemplaryembodiment. Assembly of modules 1700 can be, and in some embodiments is,used in DNS server 1600. The modules in the assembly of modules 1700can, and in some embodiments are, implemented fully in hardware withinthe processor 1602, e.g., as individual circuits. The modules in theassembly of modules 1600 can, and in some embodiments are, implementedfully in hardware within the assembly of modules 1610, e.g., asindividual circuits corresponding to the different modules. In otherembodiments some of the modules are implemented, e.g., as circuits,within the processor 1602 with other modules being implemented, e.g., ascircuits within assembly of modules 1610, external to and coupled to theprocessor 1602. As should be appreciated the level of integration ofmodules on the processor and/or with some modules being external to theprocessor may be one of design choice. Alternatively, rather than beingimplemented as circuits, all or some of the modules may be implementedin software and stored in the memory 1604 of the DNS server 1600, withthe modules controlling operation of DNS server 1600 to implement thefunctions corresponding to the modules when the modules are executed bya processor, e.g., processor 1602. In some such embodiments, theassembly of modules 1700 is included in the memory 1604 as assembly ofmodules 1616. In still other embodiments, various modules in assembly ofmodules 1700 are implemented as a combination of hardware and software,e.g., with another circuit external to the processor providing input tothe processor 1602 which then under software control operates to performa portion of a module's function. While shown in the FIG. 16 embodimentas a single processor, e.g., computer, it should be appreciated that theprocessor 1602 may be implemented as one or more processors, e.g.,computers.

When implemented in software the modules include code, which whenexecuted by the processor 1602, configure the processor 1602 toimplement the function corresponding to the module. In embodiments wherethe assembly of modules 1700 is stored in the memory 1604, the memory1604 is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each module, for causing atleast one computer, e.g., processor 1602, to implement the functions towhich the modules correspond.

Completely hardware based or completely software based modules may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented modules may be used to implementthe functions. As should be appreciated, the modules illustrated in FIG.17 control and/or configure the DNS server 1600 or elements therein suchas the processor 1602, to perform the functions of corresponding stepsillustrated in the method of one or more of the signaling drawing ofFIG. 2-5 and/or one or more of the flowcharts of FIGS. 6-10. Thus theassembly of modules 1700 includes various modules that perform functionsof corresponding steps of one or more of FIGS. 2-10.

Assembly of modules 1700 includes a module 1702 configured to receive arequest to resolve a name corresponding to a tracking area identifiercorresponding to the area in which the access point is located, and amodule 1703 configured to respond to the request to resolve the namewith an IP address or a domain name and an IP address corresponding to adata center. In some embodiments, module 1703 includes a module 1704configured to respond to the request to resolve the name with an IPaddress or a domain name and an IP address corresponding to a seconddata center which is different from the first data center. In variousembodiments, module 1704 includes a module 1706 configured to send apriority indicator indicating that the response has a lower prioritythan a response that may be provided by a primary DNS server. In variousembodiments, module 1704 includes a module 1707 configured to send apriority indicator indicating that the response has a higher prioritythan a response that may be provided by a primary DNS server, e.g., thepriority may have been updated in response to a received dynamic DNSupdate message so that the secondary DNS server will have higherpriority than the primary DNS server. Assembly of modules 1700 furtherincludes a module 1708 configured to receive a DNS update message, e.g.,from a management device or from another DNS server. Assembly of module1700 further includes a module 1710 configured to update stored DNSinformation in response to a received DNS update message. In variousembodiments, module 1710 includes one or both of a module 1712configured to change a stored IP address or a domain name correspondingto a tracking area in which an access point is located, and a module1714 configured to change a stored priority corresponding to a trackingarea in which an access point is located. FIG. 12 and FIG. 12A eachillustrates exemplary updating which may be performed by module 1712.FIG. 13 and FIG. 13A illustrates exemplary updating which may beperformed by module 1714.

FIG. 18 is a drawing of an exemplary management device 1800 inaccordance with an exemplary embodiment. Exemplary management device1800 is, e.g., management device 125 of system 100 of FIG. 1, managementdevice 125′ of FIG. 3, management device 125″ of FIG. 4, managementdevice 125′″ of FIG. 5, and/or a management device implementing steps ofthe one or more of the methods of FIG. 6-10.

Management device 1800 includes a processor 1802, e.g., a CPU, memory1804, and an assembly of modules 1810, e.g., an assembly of hardwaremodules, coupled together via a bus 1811 over which the various elementsmay exchange data and information. Management device 1800 furtherincludes an input module 1806 and an output module 1808, which arecoupled to the processor 1802. In various embodiments, the input module1806 and the output module 1808 are included as part of a communicationsinterface module 1815. In various embodiments, communications interfacemodule 1815 includes interfaces for communications with different typesof devices, e.g., DNSs, HGWs, SGWs, MMEs, HeNBs, PGWs., etc. and/orsupporting a plurality of different communications protocols. The inputmodule 1806 and/or output module 1808 may, and in some embodiments do,include a plurality of different ports and/or interfaces. Input module1806 includes one or more receivers including RX 1807. Output module1808 includes one or more transmitters including a transmitter TX 1809.

Management device 1800 receives signals including messages via inputmodule 1806. Exemplary signals received by receiver RX 1807 includemonitored signals, e.g., monitored communication signals of transportconnections between access points and HGWs, monitored heartbeat signals,monitored device status signals, monitored datacenter status signals,and monitored fault indication signals.

Management device 1800 transmits signals including messages via outputmodule 1808. Exemplary signals transmitted by transmitter TX 1809include fault notification messages, maintenance notification messages,and dynamic DNS update messages.

Memory 1804 includes routines 1812 and data/information 1814. Routines1812 includes an assembly of modules 1816.

FIG. 19 is a drawing of an assembly of modules 1900 which may beincluded in an exemplary management device in accordance with anexemplary embodiment. Assembly of modules 1900 can be, and in someembodiments is, used in management device 1800. The modules in theassembly of modules 1900 can be, and in some embodiments are,implemented fully in hardware within the processor 1802, e.g., asindividual circuits. The modules in the assembly of modules 1900 can,and in some embodiments are, implemented fully in hardware within theassembly of modules 1810, e.g., as individual circuits corresponding tothe different modules. In other embodiments some of the modules areimplemented, e.g., as circuits, within the processor 1802 with othermodules being implemented, e.g., as circuits within assembly of modules1810, external to and coupled to the processor 1802. As should beappreciated the level of integration of modules on the processor and/orwith some modules being external to the processor may be one of designchoice.

Alternatively, rather than being implemented as circuits, all or some ofthe modules may be implemented in software and stored in the memory 1804of the management device 1800, with the modules controlling operation ofmanagement device 1800 to implement the functions corresponding to themodules when the modules are executed by a processor, e.g., processor1602. In some such embodiments, the assembly of modules 1900 is includedin the memory 1804 as assembly of modules 1816. In still otherembodiments, various modules in assembly of modules 1900 are implementedas a combination of hardware and software, e.g., with another circuitexternal to the processor providing input to the processor 1802 whichthen under software control operates to perform a portion of a module'sfunction. While shown in the FIG. 18 embodiment as a single processor,e.g., computer, it should be appreciated that the processor 1802 may beimplemented as one or more processors, e.g., computers.

When implemented in software the modules include code, which whenexecuted by the processor 1802, configure the processor 1802 toimplement the function corresponding to the module. In embodiments wherethe assembly of modules 1900 is stored in the memory 1804, the memory1804 is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each module, for causing atleast one computer, e.g., processor 1802, to implement the functions towhich the modules correspond.

Completely hardware based or completely software based modules may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented modules may be used to implementthe functions. As should be appreciated, the modules illustrated in FIG.19 control and/or configure the management device 1900 or elementstherein such as the processor 1802, to perform the functions ofcorresponding steps illustrated in the method of one or more of thesignaling drawing of FIG. 2-5 and/or one or more of the flowcharts ofFIGS. 6-10. Thus the assembly of modules 1900 includes various modulesthat perform functions of corresponding steps of one or more of FIGS.2-10.

Assembly of modules 1900 includes a module 1902 configured to monitorprimary gateway communications. Module 1902 includes a module 1904configured to detect a primary gateway communications failure. Assemblyof modules 1900 further includes a module 1906 configured to detect afirst data center fault condition, a module 1908 configured to generatea fault notification message, a module 1910 configured to communicate afault notification message, a module 1912 configured to generate adynamic DNS update message, a module 1914 configured to operate themanagement device to communicate a dynamic DNS update for a trackingarea identifier correspond to a location of the access point, thedynamic DNS update including an IP address or a domain namecorresponding to a second data center which is differ from the firstdata center, a module 1916 configured to operate the management deviceto communicate a dynamic DNS update for a tracking area identifiercorresponding to the location of the access point, the dynamic DNSupdate including a change in priority, e.g., the priority of the seconddata center is increased and the priority of the first data center isdecreased. Assembly of module 1900 further includes a module 1918configured to determine that it is time for a scheduled maintenanceoperation, a module 1920 configured to communicate the dynamic update inresponse to detection of a first data center fault condition, and amodule 1922 configured to communicate the dynamic DNS update inaccordance with a scheduled maintenance operation.

FIG. 20 is a drawing of an exemplary DNS server 2000, e.g., a primaryDNS server, in accordance with an exemplary embodiment. Exemplary DNSserver 2000 is, e.g., DNS 1 118 of system 100 of FIG. 1 or FIG. 2, DNS 1118′ of FIG. 3, DNS 1 118″ of FIG. 4, DNS 1′″ 118′″ of FIG. 5, and/or anDNS implementing steps of the one or more of the methods of FIG. 6-10.

DNS server 2000, e.g., a primary DNS server, includes a processor 2002,e.g., a CPU, memory 2004, and an assembly of modules 2010, e.g., anassembly of hardware modules, coupled together via a bus 2011 over whichthe various elements may exchange data and information. DNS server 2000further includes an input module 2006 and an output module 2008, whichare coupled to the processor 2002. In various embodiments, the inputmodule 2006 and the output module 2008 are included as part of acommunications interface module 2015. In various embodiments,communications interface module 2015 includes interfaces forcommunications with different types of devices, e.g., other DNSs, HGWs,SGWs, MMES, HeNBs, management devices, etc. and/or supporting aplurality of different communications protocols. The input module 2006and/or output module 2008 may, and in some embodiments do, include aplurality of different ports and/or interfaces. Input module 2006includes one or more receivers including RX 2007. Output module 2008includes one or more transmitters including a transmitter TX 2009.

DNS server 2000 receives signals including messages via input module2006. Exemplary signals received by receiver RX 2007 include DNS requestmessages, and dynamic DNS update messages.

DNS server 2000 transmits signals including messages via output module2008. Exemplary signals transmitted by transmitter TX 2009 include DNSresponse messages.

Memory 2004 includes routines 2012 and data/information 2014. Routines2012 includes an assembly of modules 2016. Data/information 2014, insome embodiments, includes mapping information, e.g., exemplary mappingtables, such as illustrated in one or more of FIGS. 11-13.

FIG. 21 is a drawing of an assembly of modules 2100 which may beincluded in an exemplary DNS server in accordance with an exemplaryembodiment. Assembly of modules 2100 can be, and in some embodiments is,used in DNS server 2000. The modules in the assembly of modules 2100can, and in some embodiments are, implemented fully in hardware withinthe processor 2002, e.g., as individual circuits. The modules in theassembly of modules 2100 can, and in some embodiments are, implementedfully in hardware within the assembly of modules 2010, e.g., asindividual circuits corresponding to the different modules. In otherembodiments some of the modules are implemented, e.g., as circuits,within the processor 2002 with other modules being implemented, e.g., ascircuits within assembly of modules 2010, external to and coupled to theprocessor 2002. As should be appreciated the level of integration ofmodules on the processor and/or with some modules being external to theprocessor may be one of design choice. Alternatively, rather than beingimplemented as circuits, all or some of the modules may be implementedin software and stored in the memory 2004 of the DNS server 2000, withthe modules controlling operation of DNS server 2000 to implement thefunctions corresponding to the modules when the modules are executed bya processor, e.g., processor 2002. In some such embodiments, theassembly of modules 2100 is included in the memory 2004 as assembly ofmodules 2016. In still other embodiments, various modules in assembly ofmodules 1700 are implemented as a combination of hardware and software,e.g., with another circuit external to the processor providing input tothe processor 2002 which then under software control operates to performa portion of a module's function. While shown in the FIG. 20 embodimentas a single processor, e.g., computer, it should be appreciated that theprocessor 2002 may be implemented as one or more processors, e.g.,computers.

When implemented in software the modules include code, which whenexecuted by the processor 2002, configure the processor 2002 toimplement the function corresponding to the module. In embodiments wherethe assembly of modules 2100 is stored in the memory 2004, the memory2004 is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each module, for causing atleast one computer, e.g., processor 2002, to implement the functions towhich the modules correspond.

Completely hardware based or completely software based modules may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented modules may be used to implementthe functions. As should be appreciated, the modules illustrated in FIG.21 control and/or configure the DNS server 2000 or elements therein suchas the processor 2002, to perform the functions of corresponding stepsillustrated in the method of one or more of the signaling drawing ofFIG. 2-5 and/or one or more of the flowcharts of FIGS. 6-10. Thus theassembly of modules 2100 includes various modules that perform functionsof corresponding steps of one or more of FIGS. 2-10.

Assembly of modules 2100 includes a module 2102 configured to receive arequest to resolve a name corresponding to a tracking area identifiercorresponding to the area in which the access point is located, and amodule 2103 configured to respond to the request to resolve the namewith an IP address or a domain name and an IP address corresponding to adata center. In some embodiments, module 2103 includes a module 2104configured to respond to the request to resolve the name with an IPaddress or a domain name and an IP address corresponding to a first datacenter which is different from the second data center. In variousembodiments, module 2104 includes a module 2106 configured to send apriority indicator indicating that the response has a higher prioritythan a response that may be provided by a secondary DNS server. Invarious embodiments, module 2104 includes a module 2107 configured tosend a priority indicator indicating that the response has a lowerpriority than a response that may be provided by a secondary DNS server,e.g., the priority may have been updated in response to a receiveddynamic DNS update message so that the secondary DNS server will havehigher priority than the primary DNS server. Assembly of modules 2100further includes a module 2108 configured to receive a DNS updatemessage, e.g., from a management device or from another DNS server.Assembly of module 2100 further includes a module 2110 configured toupdate stored DNS information in response to a received DNS updatemessage. In various embodiments, module 2110 includes one or both of amodule 2112 configured to change a stored IP address or a domain namecorresponding to a tracking area in which an access point is located,and a module 2114 configured to change a stored priority correspondingto a tracking area in which an access point is located. FIG. 12 and FIG.12A each illustrates exemplary updating which may be performed by module2112. FIG. 13 and FIG. 13A illustrate exemplary updating which may beperformed by module 2114.

In some embodiments, assembly of modules 2100 includes a module 2116configured to control the DNS server 2000 to refrain from responding tothe request to resolve a name corresponding to a location in which theaccess point is located, in response to a detected first data centerfailure or a primary gateway communications failure.

FIG. 22 is a drawing of an exemplary DNS server 2200, e.g., a DNS serverin a service provider datacenter, in accordance with an exemplaryembodiment. Exemplary DNS server 2200 is, e.g., DNS 115 of system 100 ofFIG. 1 or FIG. 2, DNS 115′ of FIG. 3, DNS 115″ of FIG. 4, DNS 115′″ ofFIG. 5, and/or an DNS implementing steps of the one or more of themethods of FIG. 6-10.

DNS server 2200, e.g., a DNS of a service provider datacenter, includesa processor 2202, e.g., a CPU, memory 2204, and an assembly of modules2210, e.g., an assembly of hardware modules, coupled together via a bus2211 over which the various elements may exchange data and information.DNS server 2200 further includes an input module 2206 and an outputmodule 2208, which are coupled to the processor 2202. In variousembodiments, the input module 2206 and the output module 2208 areincluded as part of a communications interface module 2215. In variousembodiments, communications interface module 2215 includes interfacesfor communications with different types of devices, e.g., other DNSs,HGWs, SGWs, MMES, HeNBs, management devices, etc. and/or supporting aplurality of different communications protocols. The input module 2206and/or output module 2208 may, and in some embodiments do, include aplurality of different ports and/or interfaces. Input module 2206includes one or more receivers including RX 2207. Output module 2208includes one or more transmitters including a transmitter TX 2209.

DNS server 2200 receives signals including messages via input module2206. Exemplary signals received by receiver RX 2207 include DNS requestmessages, DNS response messages, and dynamic DNS update messages.

DNS server 2200 transmits signals including messages via output module2008. Exemplary signals transmitted by transmitter TX 2009 include DNSrequest messages and DNS response messages.

Memory 2204 includes routines 2212 and data/information 2214. Routines2212 includes an assembly of modules 2216. Data/information 2214, insome embodiments, includes mapping information, e.g., exemplary mappingtables, such as illustrated in one or more of FIGS. 11-13.

FIG. 23 is a drawing of an assembly of modules 2300 which may beincluded in an exemplary DNS server in accordance with an exemplaryembodiment. Assembly of modules 2300 can be, and in some embodiments is,used in DNS server 2200. The modules in the assembly of modules 2300can, and in some embodiments are, implemented fully in hardware withinthe processor 2202, e.g., as individual circuits. The modules in theassembly of modules 2300 can, and in some embodiments are, implementedfully in hardware within the assembly of modules 2210, e.g., asindividual circuits corresponding to the different modules. In otherembodiments some of the modules are implemented, e.g., as circuits,within the processor 2202 with other modules being implemented, e.g., ascircuits within assembly of modules 2210, external to and coupled to theprocessor 2202. As should be appreciated the level of integration ofmodules on the processor and/or with some modules being external to theprocessor may be one of design choice. Alternatively, rather than beingimplemented as circuits, all or some of the modules may be implementedin software and stored in the memory 2204 of the DNS server 2200, withthe modules controlling operation of DNS server 2200 to implement thefunctions corresponding to the modules when the modules are executed bya processor, e.g., processor 2202. In some such embodiments, theassembly of modules 2300 is included in the memory 2204 as assembly ofmodules 2216. In still other embodiments, various modules in assembly ofmodules 2300 are implemented as a combination of hardware and software,e.g., with another circuit external to the processor providing input tothe processor 2202 which then under software control operates to performa portion of a module's function. While shown in the FIG. 22 embodimentas a single processor, e.g., computer, it should be appreciated that theprocessor 2202 may be implemented as one or more processors, e.g.,computers.

When implemented in software the modules include code, which whenexecuted by the processor 2202, configure the processor 2202 toimplement the function corresponding to the module. In embodiments wherethe assembly of modules 2300 is stored in the memory 2204, the memory2204 is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each module, for causing atleast one computer, e.g., processor 2202, to implement the functions towhich the modules correspond.

Completely hardware based or completely software based modules may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented modules may be used to implementthe functions. As should be appreciated, the modules illustrated in FIG.23 control and/or configure the DNS server 2200 or elements therein suchas the processor 2202, to perform the functions of corresponding stepsillustrated in the method of one or more of the signaling drawing ofFIG. 2-5 and/or one or more of the flowcharts of FIGS. 6-10. Thus theassembly of modules 2300 includes various modules that perform functionsof corresponding steps of one or more of FIGS. 2-10.

Assembly of modules 2300 includes a module 2302 configured to receive arequest to resolve a name corresponding to a tracking area identifiercorresponding to an area in which an access point is located, a module2304 configured to forward a request to resolve a name corresponding toa tracking area identifier corresponding to an area in which an accesspoint is located to one or more DNSs, e.g., a DNS in a primarydatacenter and a DNS in a secondary datacenter, and a module 2306configured to receive DNS response information from one or more DNSs.

In some embodiments, assembly of modules 2300 includes a module 2308configured to aggregate received DNS response information; e.g.,generating a response message including the aggregated information. Insome embodiments, the aggregated information includes priorityinformation, e.g., different priority information associated with twodifferent responses from two different DNSs corresponding to twodifferent datacenters. In some embodiments, the DNS 2200 communicates aresponse message including multiple response, each including priorityinformation, to an MME, and the MME identifies the response having thehighest priority.

In some embodiments, assembly of modules 2300 includes a module 2310configured to generate a DNS response based on priority informationreceived in DNS responses, e.g., DNS server 2200 identifies andcommunicates the received response with the highest priority to the MME.In some embodiments, module 2310 includes a module 2311 configured toidentify the IP address, e.g., SGW IP address, associated with thehighest current priority among the received responses. Thus in someembodiments, the DNS 2200 filters the responses received from multipleDNS, e.g., a DNS in a primary datacenter and a DNS in a secondary datacenter, which may communicate different IP addresses, and selects andforwards the IP address corresponding to the highest current priorityamong the received alternative responses. In various embodiments, thepriority associated with a particular datacenter may be, and sometimesis changed dynamically, e.g., in response to a scheduled maintenance ora detected problem, e.g., a failure condition at a datacenter or afailure condition on a transport connection.

Assembly of modules 2300 further includes a module 2312 configured tocommunicate a DNS response message, e.g., to the MME which previouslycommunicated the corresponding request message to DNS 2200. In someembodiments, the response message may, and sometimes does, includesaggregated information corresponding to multiple DNSs. In someembodiments, the response message communicates the received responsecorresponding to the highest priority among received responses.

Assembly of modules 2300 further includes a module 2314 configured toreceive a DNS update message, e.g., a dynamic DNS update message from amanagement device, a module 2322 configured to forward informationreceived in a DNS update message, e.g., to other DNSs. Assembly ofmodules 2300 further includes a module 2316 configured to update storedDNS information in response to a received DNS update message or inresponse to information communicated from another DNS. In variousembodiments, module 2316 includes one or both of a module 2318 configurdto change a stored IP address or a domain name corresponding to atracking are in which an access point is located, and a module 2320configured to change a stored priority corresponding to a tracking areain which an access point is located.

FIG. 24 is a drawing of an exemplary Home Gateway (HGW) 2400, inaccordance with an exemplary embodiment. Exemplary HGW 2400 is, e.g.,HGW1 124 of system 100 of FIG. 1 or FIG. 2, HGW1 124′ of FIG. 3, HGW1124″ of FIG. 4, HGW1 124′″ of FIG. 5, HGW2 132 of system 100 of FIG. 1or FIG. 2, HGW2 132′ of FIG. 3, HGW2 132″ of FIG. 4, HGW2 132′″ of FIG.5, and/or a HGW implementing steps of the one or more of the methods ofFIG. 6-10.

HGW 2400, includes a processor 2402, e.g., a CPU, memory 2404, and anassembly of modules 2410, e.g., an assembly of hardware modules, coupledtogether via a bus 2411 over which the various elements may exchangedata and information. HGW 2400 further includes an input module 2406 andan output module 2408, which are coupled to the processor 2402. Invarious embodiments, the input module 2406 and the output module 2408are included as part of a communications interface module 2415. Invarious embodiments, communications interface module 2415 includesinterfaces for communications with different types of devices, e.g.,other DNSs, other HGWs, SGWs, MMEs, HeNBs, management devices, UEs, etc.and/or supporting a plurality of different communications protocols. Theinput module 2406 and/or output module 2408 may, and in some embodimentsdo, include a plurality of different ports and/or interfaces. Inputmodule 2406 includes one or more receivers including RX 2407. Outputmodule 2408 includes one or more transmitters including a transmitter TX2409.

HGW 2400 receives signals including messages via input module 2406.Exemplary signals received by receiver RX 2407 include primary transportconnection establishment signals, secondary transport connectionestablishment signals, transport connection status signals, transportconnection heartbeat signals, path switch request messages, path switchrequest acknowledgment messages, and UE context release requestmessages.

HGW 2400 transmits signals including messages via output module 2408.Exemplary signals transmitted by transmitter TX 2409 include primarytransport connection establishment signals, secondary transportconnection establishment signals, transport connection status signals,transport connection heartbeat signals, path switch request messageswhich are being forwarded, path switch request acknowledgment messageswhich are being forwarded, and UE context release request messages.

Memory 2404 includes routines 2412 and data/information 2414. Routines2412 includes an assembly of modules 2416.

FIG. 25 is a drawing of an assembly of modules 2500 which may beincluded in an exemplary HGW 2400 in accordance with an exemplaryembodiment. Assembly of modules 2500 can be, and in some embodiments is,used in HGW 2400. The modules in the assembly of modules 2500 can, andin some embodiments are, implemented fully in hardware within theprocessor 2402, e.g., as individual circuits. The modules in theassembly of modules 2500 can, and in some embodiments are, implementedfully in hardware within the assembly of modules 2410, e.g., asindividual circuits corresponding to the different modules. In otherembodiments some of the modules are implemented, e.g., as circuits,within the processor 2402 with other modules being implemented, e.g., ascircuits within assembly of modules 2410, external to and coupled to theprocessor 2402. As should be appreciated the level of integration ofmodules on the processor and/or with some modules being external to theprocessor may be one of design choice. Alternatively, rather than beingimplemented as circuits, all or some of the modules may be implementedin software and stored in the memory 2404 of the HGW 2400, with themodules controlling operation of HGW 2400 to implement the functionscorresponding to the modules when the modules are executed by aprocessor, e.g., processor 2402. In some such embodiments, the assemblyof modules 2500 is included in the memory 2404 as assembly of modules2416. In still other embodiments, various modules in assembly of modules2500 are implemented as a combination of hardware and software, e.g.,with another circuit external to the processor providing input to theprocessor 2402 which then under software control operates to perform aportion of a module's function. While shown in the FIG. 24 embodiment asa single processor, e.g., computer, it should be appreciated that theprocessor 2402 may be implemented as one or more processors, e.g.,computers.

When implemented in software the modules include code, which whenexecuted by the processor 2402, configure the processor 2402 toimplement the function corresponding to the module. In embodiments wherethe assembly of modules 2500 is stored in the memory 2404, the memory2404 is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each module, for causing atleast one computer, e.g., processor 2402, to implement the functions towhich the modules correspond.

Completely hardware based or completely software based modules may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented modules may be used to implementthe functions. As should be appreciated, the modules illustrated in FIG.25 control and/or configure the HGW 2400 or elements therein such as theprocessor 2402, to perform the functions of corresponding stepsillustrated in the method of one or more of the signaling drawing ofFIG. 2-5 and/or one or more of the flowcharts of FIGS. 6-10. Thus theassembly of modules 2500 includes various modules that perform functionsof corresponding steps of one or more of FIGS. 2-10.

Assembly of modules 2500 includes a module 2502 configured to establisha gateway connection, e.g., a primary transport connection or asecondary transport connection, between an access point, e.g., a HeNB,and the gateway, e.g., HGW 2400, a module 2504 configured to communicatesignals used to detect a communications failure condition with regard toan established connection, e.g., signals including heartbeat signals, amodule 2506 configured to receive a path switch request, e.g., a pathswitch request communicated over a secondary transport connection inresponse to a detected primary gateway communications failure, a module2508 configured to forward a received path switch request to a networkentity, e.g., to a MME, a module 2510 configured to receive a pathswitch request acknowledgment, a module 2512 configured to forward areceived path switch request acknowledgment to an access point, and amodule 2514 configured to receive a UE context release request.

FIG. 26 is a drawing of an exemplary mobile node 2600, e.g., a userequipment (UE) device in accordance with an exemplary embodiment.Exemplary mobile node 2600 is, e.g., UE 134 of system 100 of FIG. 1 orFIG. 2, UE 134′ of FIG. 3, UE 134″ of FIG. 4, UE 134′″ of FIG. 5, and/ora UE implementing steps of the one or more of the methods of FIG. 6-10.

Mobile node 2600, e.g., a UE, includes a processor 2602, e.g., a CPU,memory 2604, and an assembly of modules 2610, e.g., an assembly ofhardware modules, coupled together via a bus 2609 over which the variouselements may exchange data and information. Mobile node 2600 furtherincludes an input module 2606 and an output module 2608, which arecoupled to the processor 2602. In various the input module 2606 and theoutput module 2608 are included as part of a communications interfacemodule 2615. In various embodiments, communications interface module2615 includes interfaces for communications with different types ofdevices and/or supporting a plurality of different communicationsprotocols. The input module 2606 and/or output module 2608 may, and insome embodiments do, include a plurality of different ports and/orinterfaces. Input module 2606 includes a plurality of receiversincluding a first receiver RX 1 2618, which is a wireless receivercoupled to transmit antenna 2619, and a second receiver RX 2 2620.Output module 2608 includes a plurality of transmitters including afirst transmitter TX 1 2622, which is a wireless transmitter coupled totransmit antenna 2623, and a second transmitter TX 2 1424. In someembodiments, the same antenna is used for both receive and transmit.

Mobile node 2600 receives signals including connection establishmentsignals and user data signals via RX 1 2618. Mobile node 2600 transmitssignals including connection establishment signals and user data signalsvia TX 1 2622.

Memory 2604 includes routines 2612 and data/information 2614. Routines2612 includes an assembly of modules 2616. Data information 2614includes session information and user data.

FIG. 27 is a drawing of an assembly of modules 2700 which may beincluded in an exemplary mobile node, e.g., a UE device, in accordancewith an exemplary embodiment. Assembly of modules 2700 which can, and insome embodiments is, used in the mobile node 2600. The modules in theassembly of modules 2700 can, and in some embodiments are, implementedfully in hardware within the processor 2602, e.g., as individualcircuits. The modules in the assembly of modules 2700 can, and in someembodiments are, implemented fully in hardware within the assembly ofmodules 2610, e.g., as individual circuits corresponding to thedifferent modules. In other embodiments some of the modules areimplemented, e.g., as circuits, within the processor 2602 with othermodules being implemented, e.g., as circuits within assembly of modules2610, external to and coupled to the processor 2602. As should beappreciated the level of integration of modules on the processor and/orwith some modules being external to the processor may be one of designchoice.

Alternatively, rather than being implemented as circuits, all or some ofthe modules may be implemented in software and stored in the memory 2604of the mobile node 2600, with the modules controlling operation ofmobile node 2600 to implement the functions corresponding to the moduleswhen the modules are executed by a processor, e.g., processor 2602. Insome such embodiments, the assembly of modules 2700 is included in thememory 2604 as assembly of modules 2616. In still other embodiments,various modules in assembly of modules 2700 are implemented as acombination of hardware and software, e.g., with another circuitexternal to the processor providing input to the processor 2602 whichthen under software control operates to perform a portion of a module'sfunction. While shown in the FIG. 26 embodiment as a single processor,e.g., computer, it should be appreciated that the processor 2602 may beimplemented as one or more processors, e.g., computers.

When implemented in software the modules include code, which whenexecuted by the processor 2602, configure the processor 2602 toimplement the function corresponding to the module. In embodiments wherethe assembly of modules 2700 is stored in the memory 2604, the memory2604 is a computer program product comprising a computer readable mediumcomprising code, e.g., individual code for each module, for causing atleast one computer, e.g., processor 2602, to implement the functions towhich the modules correspond.

Completely hardware based or completely software based modules may beused. However, it should be appreciated that any combination of softwareand hardware, e.g., circuit implemented modules may be used to implementthe functions. As should be appreciated, the modules illustrated in FIG.27 control and/or configure the mobile node 2600 or elements thereinsuch as the processor 2602, to perform the functions of correspondingsteps illustrated in the method of one or more of the signaling drawingof FIG. 2-5 and/or one or more of the flowcharts of FIGS. 6-10. Thus theassembly of modules 2700 includes various modules that perform functionsof corresponding steps of one or more of FIGS. 2-10.

Assembly of modules 2700 includes a module 2702 configured to establisha connection with an access point, e.g., a UE connection with an HeNB,and a module 2704 configured to communicate user data over theestablished connection.

An exemplary communications method, in accordance with some embodiments,comprises: establishing a primary gateway connection between an accesspoint, e.g., a HeNB, and a primary gateway; establishing a connectionfor a user equipment (UE) device to said access point, said establishedconnection being between said UE device and said access point; andtransmitting a path switch request via a secondary gateway connectionbetween said access point and a secondary gateway, to a network entity,e.g., a MME, for said UE device connected to said access point whilesaid UE device remains connected to said access point.

In some embodiments, the primary gateway connection is a transport layerconnection, and the secondary gateway connection is a transport layerconnection.

In some embodiments, the access point is an LTE HeNB. In variousembodiments, the path switch request is a request to update data andsignaling paths corresponding to the UE device. In some embodiments,said path switch request is an LTE S1AP Path Switch Request.

In some embodiments, the UE device is connected to one cell of saidaccess point prior to and subsequent to said path switch request.

In various embodiments, the exemplary method includes transmitting acontext release request for said UE device to the primary gatewayfollowing transmission of said path switch request.

In some embodiments, the exemplary method includes detecting, at saidaccess point or a management device, a primary gateway communicationfailure; and the path switch request is sent via the secondary gatewayconnection in response to detecting the primary gateway communicationfailure. In some such embodiments, the primary gateway is located in afirst data center; and the exemplary method further includes receivingat a DNS server a request to resolve a name corresponding to a trackingarea identifier corresponding to the area in which the access point islocated; and responding to said request to resolve the name with an IPaddress or a domain name and an IP address, corresponding to a seconddata center which is different from said first data center.

In some embodiments, said DNS server is located at said second datacenter.

In some embodiments, responding, at the DNS server that received saidrequest, to said request to resolve a name includes sending a priorityindicator indicating that the response has a lower priority than aresponse that may be provided by a primary DNS server. In some suchembodiments, the primary DNS server is located at the first data center.

In various embodiments, the first and second data centers correspond todifferent sets of physical equipment. In some such embodiments, thefirst and second data centers are located in different buildings.

In various embodiments, the exemplary method includes receiving, at theaccess point, a response to the path switch request from the networkentity via the secondary gateway connection. In some such embodiments,the exemplary method further includes sending, in response to receivingthe path switch request response, a UE context release message for saidUE over the primary connection to the primary gateway. In some suchembodiments, the secondary gateway is located at the secondary datacenter.

In some embodiments, the primary gateway is located in a first datacenter; and the exemplary method further includes operating themanagement device to communicate a dynamic DNS update for a trackingarea identifier corresponding to a location of the access point, saiddynamic DNS update including an IP address or a domain namecorresponding to a second data center which is different from first datacenter. In some such embodiments, the first and second data centerscorrespond to different sets of physical equipment. In some suchembodiments, the first and second data centers are located in differentbuildings.

In various embodiments, the management device communicates the dynamicDNS update in response to detection of a first data center faultcondition. In some embodiments, said management device communicates thedynamic DNS update in accordance with a scheduled maintenance operationon the first data center.

An exemplary communications system, in accordance with some embodiments,includes: an access point, e.g, a HeNB, comprising: a module configuredto establish a primary gateway connection between the access point and aprimary gateway; a module configured to establish a connection for auser equipment (UE) device to said access point, said establishedconnection being between said UE device and said access point; atransmitter; and a module configured to control the transmitter totransmit a path switch request via a secondary gateway connectionbetween said access point and a secondary gateway, to a network entity,e.g., a MME, for said UE device connected to said access point whilesaid UE device remains connected to said access point. In some suchembodiments, the access point is an LTE HeNB. In some embodiments, theprimary gateway connection and the second gateway connection aretransport layer connections.

In various embodiments, said path switch request is a request to updatedata and signaling paths corresponding to the UE device. In someembodiments, said path switch request is an LTE S1AP Path SwitchRequest.

In some embodiments, the UE device is connected to one cell of saidaccess point prior to and subsequent to said path switch request.

In some embodiments, the access point in the exemplary communicationssystem further includes a module configured to control the transmitterto transmit a context release request for said UE device to the primarygateway following transmission of said path switch request.

In some embodiments, the access point further includes: a moduleconfigured to detecting a primary gateway communication failure; and themodule configured to control the transmitter to transmit a path switchrequest path switch request is further configured to control thetransmitter to transmit the path switch request in response to detectingthe primary gateway communication failure.

The communications system, in some embodiments, further includes amanagement device, and the management device includes: a moduleconfigured to detect a primary gateway communication failure; and thepath switch request is sent via the secondary gateway connection inresponse to a detected the primary gateway communication failure by themanagement device. In some such embodiments, the primary gateway islocated in a first data center; and the communications system furtherincludes a DNS server comprising: a module configured to receive arequest to resolve a name corresponding to a tracking area identifiercorresponding to the area in which the access point is located; and amodule configured to respond to said request to resolve the name with anIP address or a domain name and an IP address corresponding to a seconddata center which is different from said first data center. In some suchembodiments, the DNS server is located at said second data center.

In various embodiments, the module configured to respond to said requestto resolve a name includes: a module configured to send a priorityindicator indicating that the response has a lower priority than aresponse that may be provided by a primary DNS server.

In various embodiments, the primary DNS server is located at the firstdata center. In some embodiments, the first and second data centerscorrespond to different sets of physical equipment. In some suchembodiments, the first and second data centers are located in differentbuildings.

In some embodiments, the access point further includes a moduleconfigured to receive, at the access point, a response to the pathswitch request from the network entity via the secondary gatewayconnection. In some such embodiments, the access point further includesa module configured to send, in response to receiving the path switchrequest response, a UE context release message for said UE over theprimary connection to the primary gateway. In some such embodiments, thesecondary gateway is located at the secondary data center.

In various embodiments, the primary gateway is located in a first datacenter; and the communications system includes a management device, andthe management device includes a module configured to operate themanagement device to communicate a dynamic DNS update for a trackingarea identifier corresponding to a location of the access point, saiddynamic DNS update including an IP address or a domain namecorresponding to a second data center which is different from first datacenter. In some such embodiments, the first and second data centerscorrespond to different sets of physical equipment. In some embodiments,the first and second data centers are located in different buildings.

In some embodiments, the management device includes a module configuredto communicates the dynamic DNS update in response to detection of afirst data center fault condition. In some embodiments, the managementdevice includes a module configured to communicates the dynamic DNSupdate in accordance with a scheduled maintenance operation on the firstdata center.

The techniques of various embodiments may be implemented using software,hardware and/or a combination of software and hardware. Variousembodiments are directed to apparatus, e.g., communications device suchas home gateway (HGW), access point, e.g., an HeNB, a mobilitymanagement entity (MME), serving gateway (SGW), and/or a user equipment(UE) device, a management device, a domain name server (DNS), etc.Various embodiments are also directed to methods, e.g., a method ofoperating a communications device such as a home gateway (HGW), accesspoint, e.g., an HeNB, a mobility management entity (MME), servinggateway (SGW), a domain name server (DNS), a management device, and/or auser equipment (UE) device, etc. Various embodiments are also directedto machine, e.g., computer, readable medium, e.g., ROM, RAM, CDs, harddiscs, etc., which include machine readable instructions for controllinga machine to implement one or more steps of a method. The computerreadable medium is, e.g., non-transitory computer readable medium.

It is understood that the specific order or hierarchy of steps in theprocesses disclosed is an example of exemplary approaches. Based upondesign preferences, it is understood that the specific order orhierarchy of steps in the processes may be rearranged while remainingwithin the scope of the present disclosure. The accompanying methodclaims present elements of the various steps in a sample order, and arenot meant to be limited to the specific order or hierarchy presented.

In various embodiments nodes described herein are implemented using oneor more modules to perform the steps corresponding to one or moremethods, for example, making a handover type decision, implementing thedecision, signal generation, signal transmission, signal reception,signal processing, and/or other steps. Thus, in some embodiments variousfeatures are implemented using modules. Such modules may be implementedusing software, hardware or a combination of software and hardware. Manyof the above described methods or method steps can be implemented usingmachine executable instructions, such as software, included in a machinereadable medium such as a memory device, e.g., RAM, floppy disk, etc. tocontrol a machine, e.g., general purpose computer with or withoutadditional hardware, to implement all or portions of the above describedmethods, e.g., in one or more nodes. Accordingly, among other things,various embodiments are directed to a machine-readable medium, e.g., anon-transitory computer readable medium, including machine executableinstructions for causing a machine, e.g., processor and associatedhardware, to perform one or more of the steps of the above-describedmethod(s). Some embodiments are directed to an apparatus, e.g., acommunications device such as a gateway, e.g., a Home Gateway (HGW),including a processor configured to implement one, multiple or all ofthe steps of one or more methods of the invention.

In some embodiments, the processor or processors, e.g., CPUs, of one ormore devices, e.g., of the communications device, e.g., an access pointsuch as a HeNB, a gateway such as a HGW, a DNS server, a managementdevice are configured to perform the steps of the methods described asbeing performed by the apparatus. The configuration of the processor maybe achieved by using one or more modules, e.g., software modules, tocontrol processor configuration and/or by including hardware in theprocessor, e.g., hardware modules, to perform the recited steps and/orcontrol processor configuration. Accordingly, some but not allembodiments are directed to a device, e.g., such as communicationsdevice with a processor which includes a module corresponding to each ofthe steps of the various described methods performed by the device inwhich the processor is included. In some but not all embodiments anapparatus, e.g., a communications device includes a module correspondingto each of the steps of the various described methods performed by thedevice in which the processor is included. The modules may beimplemented using software and/or hardware.

Some embodiments are directed to a computer program product comprising acomputer-readable medium, e.g., a non-transitory computer-readablemedium, comprising code for causing a computer, or multiple computers,to implement various functions, steps, acts and/or operations, e.g. oneor more steps described above. Depending on the embodiment, the computerprogram product can, and sometimes does, include different code for eachstep to be performed. Thus, the computer program product may, andsometimes does, include code for each individual step of a method, e.g.,a method of controlling a communications device. The code may be in theform of machine, e.g., computer, executable instructions stored on acomputer-readable medium, e.g., a non-transitory computer-readablemedium, such as a RAM (Random Access Memory), ROM (Read Only Memory) orother type of storage device. In addition to being directed to acomputer program product, some embodiments are directed to a processorconfigured to implement one or more of the various functions, steps,acts and/or operations of one or more methods described above.Accordingly, some embodiments are directed to a processor, e.g., CPU,configured to implement some or all of the steps of the methodsdescribed herein.

Various features are directed to a system including multiple networknodes or components including, for example, one or more servers and oneor more access points, e.g., HeNBs and/or other network nodes orentities. In various embodiments the network nodes or entites areimplemented as hardware, e.g., separate devices each including acommunications interface for sending and/or receiving signalscommunicating data or other information, one or more processors andmemory. In some embodiments the memory includes data and/or controlroutines. In at least some embodiments the one or more processorsoperate under control instructions in the control routine or routinesstored in the node's memory. thus, when executed by the processor, theinstructions in the node or other network entity to perform thefunctions in accordance with one or more of the methods describedherein. In some embodiments the processor or processors of individualnodes are special purposed processors, e.g., ASICs, with hardwarecircuitry which is configured to implement or control the node ornetwork entity in which the special purpose processor is located toimplement one or more steps in accordance with a method or methodsdescribed herein. In at least some embodiments, circuits and/or otherhardware are used to implement the node or method resulting in a fullyhardware implemented embodiment.

Numerous additional variations on the methods and apparatus of thevarious embodiments described above will be apparent to those skilled inthe art in view of the above description. Such variations are to beconsidered within the scope. Numerous additional embodiments, within thescope of the present invention, will be apparent to those of ordinaryskill in the art in view of the above description and the claims whichfollow. Such variations are to be considered within the scope of theinvention.

What is claimed is:
 1. A communications method, the method comprising:establishing a primary gateway connection between an access point and aprimary gateway; establishing a connection for a user equipment (UE)device to said access point, said established connection being betweensaid UE device and said access point; and transmitting a path switchrequest via a secondary gateway connection between said access point anda secondary gateway, to a network entity, for said UE device connectedto said access point while said UE device remains connected to saidaccess point.